Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6418bfa282fbdc426b04b71aa7aa204ade2765d31b10e2119257e31a7406a3aa

Tx prefix hash: e63d1ef6b27b6f0068630930de058323428bebed67fbd95209f445e2a6f4f53a
Tx public key: 73fd4d20c9450b57b1614a000982604c637b5d6fecaa6b8e359caf8ceaf7238a
Timestamp: 1727223548 Timestamp [UCT]: 2024-09-25 00:19:08 Age [y:d:h:m:s]: 00:197:05:34:44
Block: 1117438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140779 RingCT/type: yes/0
Extra: 0173fd4d20c9450b57b1614a000982604c637b5d6fecaa6b8e359caf8ceaf7238a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06aec0aa46ca93a4bf0d980526cb79df64e6e88c6d1b0403efede0bf34517ddf 0.600000000000 1598277 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": 1117448, "vin": [ { "gen": { "height": 1117438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06aec0aa46ca93a4bf0d980526cb79df64e6e88c6d1b0403efede0bf34517ddf" } } ], "extra": [ 1, 115, 253, 77, 32, 201, 69, 11, 87, 177, 97, 74, 0, 9, 130, 96, 76, 99, 123, 93, 111, 236, 170, 107, 142, 53, 156, 175, 140, 234, 247, 35, 138, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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