Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffd4eddb6fbf77db56c6609829d799b5fa33ab3a7b5267a004451f9a9cba312

Tx prefix hash: 0cfdb3ed293c6bf2b050ba67fc16a44569e206f179a79a79d760df12776e07bc
Tx public key: fe3ea81c112dc638d0f449bd132410f88bbc4fe2c22c7c5eec15d7e71cef244d
Timestamp: 1765140494 Timestamp [UCT]: 2025-12-07 20:48:14 Age [y:d:h:m:s]: 00:027:19:13:30
Block: 1428663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19920 RingCT/type: yes/0
Extra: 01fe3ea81c112dc638d0f449bd132410f88bbc4fe2c22c7c5eec15d7e71cef244d0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35a5baedebf8af7ea13c1e25c70ac0650dcc8f5630f9fda8e9448350f6e5797 0.600000000000 1917386 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": 1428673, "vin": [ { "gen": { "height": 1428663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35a5baedebf8af7ea13c1e25c70ac0650dcc8f5630f9fda8e9448350f6e5797" } } ], "extra": [ 1, 254, 62, 168, 28, 17, 45, 198, 56, 208, 244, 73, 189, 19, 36, 16, 248, 139, 188, 79, 226, 194, 44, 124, 94, 236, 21, 215, 231, 28, 239, 36, 77, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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