Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2487897f9a7ac1cb7d2d885df4b72488e7508e4c72352fa5687e706f32d9548d

Tx prefix hash: 165c5135729cce2fbd73aecf768c58da7101e1b1511dc695c728189f524e9afe
Tx public key: 4ab1c1edcafce78e2d13b5bd36607330ddceb20ce95b417086a0eef5dc77ee47
Timestamp: 1715731465 Timestamp [UCT]: 2024-05-15 00:04:25 Age [y:d:h:m:s]: 00:329:09:13:53
Block: 1022172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235438 RingCT/type: yes/0
Extra: 014ab1c1edcafce78e2d13b5bd36607330ddceb20ce95b417086a0eef5dc77ee47021100000001c5452960000000000000000000

1 output(s) for total of 0.613570000000 dcy

stealth address amount amount idx
00: 1e95d3654d6e70f708f8b8e805368e5d3340cbd275cb2800e9ff2ca87b00a70d 0.613570000000 1486693 of 0

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": 1022182, "vin": [ { "gen": { "height": 1022172 } } ], "vout": [ { "amount": 613570000, "target": { "key": "1e95d3654d6e70f708f8b8e805368e5d3340cbd275cb2800e9ff2ca87b00a70d" } } ], "extra": [ 1, 74, 177, 193, 237, 202, 252, 231, 142, 45, 19, 181, 189, 54, 96, 115, 48, 221, 206, 178, 12, 233, 91, 65, 112, 134, 160, 238, 245, 220, 119, 238, 71, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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