Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5737f8c5c470cb12c9b3c3283dcaea65e3f27b78c3fd7ccabde53f56128d200b

Tx prefix hash: 671b46f8baf35ecb1159fe1c126c62b0acf8a3c4e4d48e2f971c6dd539cb8b9d
Tx public key: 1493ae7ff92b3f07592a71f5219d0d24744785c504b3e5db529814d1068fb97f
Timestamp: 1762527162 Timestamp [UCT]: 2025-11-07 14:52:42 Age [y:d:h:m:s]: 00:046:07:56:50
Block: 1407004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33160 RingCT/type: yes/0
Extra: 011493ae7ff92b3f07592a71f5219d0d24744785c504b3e5db529814d1068fb97f021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecc37ff4b45aace7b5ccb9ad14d3cabd8c1b4b2a9b55adc40f8a9a70cc65480a 0.600000000000 1895393 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": 1407014, "vin": [ { "gen": { "height": 1407004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecc37ff4b45aace7b5ccb9ad14d3cabd8c1b4b2a9b55adc40f8a9a70cc65480a" } } ], "extra": [ 1, 20, 147, 174, 127, 249, 43, 63, 7, 89, 42, 113, 245, 33, 157, 13, 36, 116, 71, 133, 197, 4, 179, 229, 219, 82, 152, 20, 209, 6, 143, 185, 127, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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