Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330b3ba47ec0f84da33f80c3827f061fed41f5d9535b57c898f919875b4ade75

Tx prefix hash: adc02abe711c226b95f0514a15a3b47d6783f724567169ca1f699b67d3cf65fd
Tx public key: 45f895c22a6793bf61f8022f147fa534e155475c07e6eb20ad2c2c750e33b7c8
Timestamp: 1735455406 Timestamp [UCT]: 2024-12-29 06:56:46 Age [y:d:h:m:s]: 00:120:21:25:42
Block: 1185554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86218 RingCT/type: yes/0
Extra: 0145f895c22a6793bf61f8022f147fa534e155475c07e6eb20ad2c2c750e33b7c8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f60e9a98b9e62cda9171d8fadcf5d1c6ea869b7851d297fc889a8c76d3ddd9b 0.600000000000 1672027 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": 1185564, "vin": [ { "gen": { "height": 1185554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f60e9a98b9e62cda9171d8fadcf5d1c6ea869b7851d297fc889a8c76d3ddd9b" } } ], "extra": [ 1, 69, 248, 149, 194, 42, 103, 147, 191, 97, 248, 2, 47, 20, 127, 165, 52, 225, 85, 71, 92, 7, 230, 235, 32, 173, 44, 44, 117, 14, 51, 183, 200, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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