Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8b00ee3566afc89bc809e9a16763c960156c0811cd33792f2d0d12f72cd8a07a

Tx prefix hash: b664ebefb20dc82df4e6449a958805b9659974a3a4cbb9ae04b9ecbe628c3661
Tx public key: ab23c0e4e505e3233e800662fcd8627a4c1d86770437a2f4eab2f0a5bdcc923c
Timestamp: 1626781671 Timestamp [UCT]: 2021-07-20 11:47:51 Age [y:d:h:m:s]: 03:170:20:44:39
Block: 297561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893785 RingCT/type: yes/0
Extra: 01ab23c0e4e505e3233e800662fcd8627a4c1d86770437a2f4eab2f0a5bdcc923c0211000001db6367b7e9000000000000000000

1 output(s) for total of 63.395346166000 dcy

stealth address amount amount idx
00: c2d2649cdaaa879766271c9b5f40cecdbd7c453e45f8a7f81f31cd9527a03c3e 63.395346166000 622779 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 297571, "vin": [ { "gen": { "height": 297561 } } ], "vout": [ { "amount": 63395346166, "target": { "key": "c2d2649cdaaa879766271c9b5f40cecdbd7c453e45f8a7f81f31cd9527a03c3e" } } ], "extra": [ 1, 171, 35, 192, 228, 229, 5, 227, 35, 62, 128, 6, 98, 252, 216, 98, 122, 76, 29, 134, 119, 4, 55, 162, 244, 234, 178, 240, 165, 189, 204, 146, 60, 2, 17, 0, 0, 1, 219, 99, 103, 183, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8