Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a35b213599238f89dcf437eee29b8ac2f88e61ce13f0008705cbff502cb2f3b

Tx prefix hash: e29102fbd627d36aa0fd3010908d7a9666926fe89b4ea9854a05e4a70d0c218d
Tx public key: c41647aa99abff599b7fe8d1537aae840421434a119f3433ab6e772ee36aa974
Timestamp: 1715706074 Timestamp [UCT]: 2024-05-14 17:01:14 Age [y:d:h:m:s]: 00:286:12:53:35
Block: 1021952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204782 RingCT/type: yes/0
Extra: 01c41647aa99abff599b7fe8d1537aae840421434a119f3433ab6e772ee36aa974021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e026f5c216d5a6d383f4d24524bf965236e148b2602032e2aa6be477b65266c4 0.600000000000 1486417 of 15

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": 1021962, "vin": [ { "gen": { "height": 1021952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e026f5c216d5a6d383f4d24524bf965236e148b2602032e2aa6be477b65266c4" } } ], "extra": [ 1, 196, 22, 71, 170, 153, 171, 255, 89, 155, 127, 232, 209, 83, 122, 174, 132, 4, 33, 67, 74, 17, 159, 52, 51, 171, 110, 119, 46, 227, 106, 169, 116, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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