Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf10d4ccf6f7b59c6fd3f9bc8d196ec67e9290658edbe43463657a9a840517b

Tx prefix hash: cd98e5037312386ee3085d1539755bc91e2abcd340aab8db3c6a0ce5c16db3bc
Tx public key: 9e12b70d420c7a697738ba5ae052bf3dd2b76fa71dfe3fcdaf42139cd48010fd
Timestamp: 1698661155 Timestamp [UCT]: 2023-10-30 10:19:15 Age [y:d:h:m:s]: 02:068:09:30:02
Block: 880864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568550 RingCT/type: yes/0
Extra: 019e12b70d420c7a697738ba5ae052bf3dd2b76fa71dfe3fcdaf42139cd48010fd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.740170744000 dcy

stealth address amount amount idx
00: 059fd0339b69f6a47eae07cf6157cbe162226dcea5c1e548010e9330d4c73e6a 0.740170744000 1336434 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": 880874, "vin": [ { "gen": { "height": 880864 } } ], "vout": [ { "amount": 740170744, "target": { "key": "059fd0339b69f6a47eae07cf6157cbe162226dcea5c1e548010e9330d4c73e6a" } } ], "extra": [ 1, 158, 18, 183, 13, 66, 12, 122, 105, 119, 56, 186, 90, 224, 82, 191, 61, 210, 183, 111, 167, 29, 254, 63, 205, 175, 66, 19, 156, 212, 128, 16, 253, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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