Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1ec4b228d404e60d9aa022e48e14b594ac2f3037c351ed3d96cbc397360e3fa

Tx prefix hash: 4136babd8bd463599c24384551b4317379418b14588f5a4a8531fed087b6b2f4
Tx public key: ca4565fad8a6f922e73c32d9f6a39b2f1720d522a3db4e85e7fd90f2563917b1
Timestamp: 1762150551 Timestamp [UCT]: 2025-11-03 06:15:51 Age [y:d:h:m:s]: 00:065:05:49:53
Block: 1403869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46737 RingCT/type: yes/0
Extra: 01ca4565fad8a6f922e73c32d9f6a39b2f1720d522a3db4e85e7fd90f2563917b102110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9109bf15ce2e03fa502b5bdbd7d44d9f53e79b40545fa024edb305ccb16c330 0.600000000000 1892222 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": 1403879, "vin": [ { "gen": { "height": 1403869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9109bf15ce2e03fa502b5bdbd7d44d9f53e79b40545fa024edb305ccb16c330" } } ], "extra": [ 1, 202, 69, 101, 250, 216, 166, 249, 34, 231, 60, 50, 217, 246, 163, 155, 47, 23, 32, 213, 34, 163, 219, 78, 133, 231, 253, 144, 242, 86, 57, 23, 177, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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