Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db9198818b2a8c824d18afea4910d90186022bc829ed3888022d1c74a161bb0

Tx prefix hash: a0aaf18fc881b54421a2150d7b091ad290c9c1c55ec67f5dbd1067f83febacf8
Tx public key: efda17d5991a05629587ac8d6ac6b17e96e79c5cb7fca25721f35370b7a8aef3
Timestamp: 1677453517 Timestamp [UCT]: 2023-02-26 23:18:37 Age [y:d:h:m:s]: 01:279:23:01:54
Block: 705705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461000 RingCT/type: yes/0
Extra: 01efda17d5991a05629587ac8d6ac6b17e96e79c5cb7fca25721f35370b7a8aef3021100000001835e4d22000000000000000000

1 output(s) for total of 2.816477511000 dcy

stealth address amount amount idx
00: ac0c9349a1a1503629d296c53b011772dbccd8f522ded1298e10c1a75c762101 2.816477511000 1149414 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": 705715, "vin": [ { "gen": { "height": 705705 } } ], "vout": [ { "amount": 2816477511, "target": { "key": "ac0c9349a1a1503629d296c53b011772dbccd8f522ded1298e10c1a75c762101" } } ], "extra": [ 1, 239, 218, 23, 213, 153, 26, 5, 98, 149, 135, 172, 141, 106, 198, 177, 126, 150, 231, 156, 92, 183, 252, 162, 87, 33, 243, 83, 112, 183, 168, 174, 243, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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