Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deb5ad0e838ffb91e010a7abe50069ea46e3a2b2d4363677f728544eaa48b4fd

Tx prefix hash: a5691f9a4ce97d428b4a7d98639bb041b3c29b90f6e6852d43aa0d06f0b06d2a
Tx public key: cf6cce21100081820cf3cfdb7e2c2639d019f792afb34f8fca8d3daa907a3ed3
Timestamp: 1761800044 Timestamp [UCT]: 2025-10-30 04:54:04 Age [y:d:h:m:s]: 00:063:21:27:58
Block: 1400987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45739 RingCT/type: yes/0
Extra: 01cf6cce21100081820cf3cfdb7e2c2639d019f792afb34f8fca8d3daa907a3ed3021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbb93782b74a41b5283845e457289c1c300955973ee9676a5eac17be48ed1fbb 0.600000000000 1889306 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": 1400997, "vin": [ { "gen": { "height": 1400987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb93782b74a41b5283845e457289c1c300955973ee9676a5eac17be48ed1fbb" } } ], "extra": [ 1, 207, 108, 206, 33, 16, 0, 129, 130, 12, 243, 207, 219, 126, 44, 38, 57, 208, 25, 247, 146, 175, 179, 79, 143, 202, 141, 61, 170, 144, 122, 62, 211, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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