Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596526744598e1de70de8bb56c888f15e635c8482b8d7bf5551c432c495180b6

Tx prefix hash: a9f1785da79f5dad0434d6c5ca4feb9a4e2bb420267ce6217e5e0fc7020d611f
Tx public key: 5c7d405434ba0838f71fd583bd90c9c310a9a3d43878cc996a509ab48ac26214
Timestamp: 1700033241 Timestamp [UCT]: 2023-11-15 07:27:21 Age [y:d:h:m:s]: 01:147:15:22:32
Block: 892016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366705 RingCT/type: yes/0
Extra: 015c7d405434ba0838f71fd583bd90c9c310a9a3d43878cc996a509ab48ac26214021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.679799270000 dcy

stealth address amount amount idx
00: 973cf9468cf4ab551e2e54c1ce0cfa83f7f51a8800218bdb30ec95c33c16dac2 0.679799270000 1348075 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": 892026, "vin": [ { "gen": { "height": 892016 } } ], "vout": [ { "amount": 679799270, "target": { "key": "973cf9468cf4ab551e2e54c1ce0cfa83f7f51a8800218bdb30ec95c33c16dac2" } } ], "extra": [ 1, 92, 125, 64, 84, 52, 186, 8, 56, 247, 31, 213, 131, 189, 144, 201, 195, 16, 169, 163, 212, 56, 120, 204, 153, 106, 80, 154, 180, 138, 194, 98, 20, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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