Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0051bee1d84252da3bdba93d1d4ca23964dd44a958f1656e0367fb5a0b239822

Tx prefix hash: b6b3c1da2cae4ed2be9bb1d94e98d949fd3c00c701f197b7cd46fd02465faa06
Tx public key: 50cfeba9b6d670f5deba64fde7a5494193d556319195f1fe90e4acb5b332f2e4
Timestamp: 1764207323 Timestamp [UCT]: 2025-11-27 01:35:23 Age [y:d:h:m:s]: 00:066:08:30:28
Block: 1420921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47334 RingCT/type: yes/0
Extra: 0150cfeba9b6d670f5deba64fde7a5494193d556319195f1fe90e4acb5b332f2e40211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3232e154f6da1a5bfcfa0464ef2c49ae3ec44ab76e88104599fb559933523eb5 0.600000000000 1909476 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": 1420931, "vin": [ { "gen": { "height": 1420921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3232e154f6da1a5bfcfa0464ef2c49ae3ec44ab76e88104599fb559933523eb5" } } ], "extra": [ 1, 80, 207, 235, 169, 182, 214, 112, 245, 222, 186, 100, 253, 231, 165, 73, 65, 147, 213, 86, 49, 145, 149, 241, 254, 144, 228, 172, 181, 179, 50, 242, 228, 2, 17, 0, 0, 0, 1, 78, 123, 252, 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