Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b7079618034cbd773e0c419833b82ed847f7a8fc5e3d3f17a759ffdfadf00b

Tx prefix hash: 404f03aa7b1d5ddb2017c142d5d26ec3dca4115c546488f046519c7133df427b
Tx public key: 407a8fedfd31243eb5b2f1a36a2ca732c5bf36a25f864f80143f10016d64adae
Timestamp: 1763195127 Timestamp [UCT]: 2025-11-15 08:25:27 Age [y:d:h:m:s]: 00:012:22:59:55
Block: 1412530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9285 RingCT/type: yes/0
Extra: 01407a8fedfd31243eb5b2f1a36a2ca732c5bf36a25f864f80143f10016d64adae02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ef860cc0d6e4f72340588fe08e27d74bc21a2977ab51c34cfa6d07fca1780b 0.600000000000 1901001 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": 1412540, "vin": [ { "gen": { "height": 1412530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ef860cc0d6e4f72340588fe08e27d74bc21a2977ab51c34cfa6d07fca1780b" } } ], "extra": [ 1, 64, 122, 143, 237, 253, 49, 36, 62, 181, 178, 241, 163, 106, 44, 167, 50, 197, 191, 54, 162, 95, 134, 79, 128, 20, 63, 16, 1, 109, 100, 173, 174, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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