Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d49bcf247ef7f5b2ea34cefee7fd691c7b33dcacb4a68e8154da8d1872ce0c1

Tx prefix hash: 2e297f7d1d714dbe6dd0b1d66e159a3bc5816c37375c96cb166c3ac26c6b2c7d
Tx public key: 491fb16ae8ba717a8d482133adedbe6ef579dab669e60f093c62b8d7fd617e21
Timestamp: 1761716974 Timestamp [UCT]: 2025-10-29 05:49:34 Age [y:d:h:m:s]: 00:022:18:31:42
Block: 1400298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16280 RingCT/type: yes/0
Extra: 01491fb16ae8ba717a8d482133adedbe6ef579dab669e60f093c62b8d7fd617e21021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ecfb98351c9864fd53ae7380008f9120c5efdf5c1124a94015249ae9b82aee0 0.600000000000 1888605 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": 1400308, "vin": [ { "gen": { "height": 1400298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ecfb98351c9864fd53ae7380008f9120c5efdf5c1124a94015249ae9b82aee0" } } ], "extra": [ 1, 73, 31, 177, 106, 232, 186, 113, 122, 141, 72, 33, 51, 173, 237, 190, 110, 245, 121, 218, 182, 105, 230, 15, 9, 60, 98, 184, 215, 253, 97, 126, 33, 2, 17, 0, 0, 0, 3, 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