Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ff29a023501368efba831173c27aaeb4318e65e9360683d00ab4d384e816d2

Tx prefix hash: bdcaee5888de8c16bb49de7a80963c2bc5a7819766d60c48dabd5d9892276084
Tx public key: 8361b20369e41f2a56e4d48c3bab47f9c1cee7b3641e7ebdcf7a07f84a1d598a
Timestamp: 1714584094 Timestamp [UCT]: 2024-05-01 17:21:34 Age [y:d:h:m:s]: 00:195:20:00:07
Block: 1012661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140187 RingCT/type: yes/0
Extra: 018361b20369e41f2a56e4d48c3bab47f9c1cee7b3641e7ebdcf7a07f84a1d598a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf413f94e8e8e42f2fc8a5712fd7fecb789f358b715ff2d422b055582555f755 0.600000000000 1475253 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": 1012671, "vin": [ { "gen": { "height": 1012661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf413f94e8e8e42f2fc8a5712fd7fecb789f358b715ff2d422b055582555f755" } } ], "extra": [ 1, 131, 97, 178, 3, 105, 228, 31, 42, 86, 228, 212, 140, 59, 171, 71, 249, 193, 206, 231, 179, 100, 30, 126, 189, 207, 122, 7, 248, 74, 29, 89, 138, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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