Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c1030d78d3dcc44302fddbe3a7d2f2ff2b3428b9479c9bab0b5769079be4af0

Tx prefix hash: 651b4355202d3f21ca1361501a5fe995a5e84178972e3a4299775da24eb42038
Tx public key: e6e504a4024cd22ae317274c2f4db6da82da82bee15555a2afaea4369ded9a39
Timestamp: 1701981716 Timestamp [UCT]: 2023-12-07 20:41:56 Age [y:d:h:m:s]: 01:102:14:08:54
Block: 908180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334475 RingCT/type: yes/0
Extra: 01e6e504a4024cd22ae317274c2f4db6da82da82bee15555a2afaea4369ded9a39021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600928260000 dcy

stealth address amount amount idx
00: ad118bfc6a77b8b74030964504097dc893187241c95e193e2b6e60f2eb7d29e2 0.600928260000 1365207 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": 908190, "vin": [ { "gen": { "height": 908180 } } ], "vout": [ { "amount": 600928260, "target": { "key": "ad118bfc6a77b8b74030964504097dc893187241c95e193e2b6e60f2eb7d29e2" } } ], "extra": [ 1, 230, 229, 4, 164, 2, 76, 210, 42, 227, 23, 39, 76, 47, 77, 182, 218, 130, 218, 130, 190, 225, 85, 85, 162, 175, 174, 164, 54, 157, 237, 154, 57, 2, 17, 0, 0, 0, 2, 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