Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f0316bff6948ceac8ec933bf86e272e5e78c3d26a3748b0e0185239f4eb7ae

Tx prefix hash: 594401b288bb0c22f619f95ac16c87e8606fbe997f98fe9f791f3531ae5dbc4f
Tx public key: 4823f3fe03772ec6fbbf188087d9863c1b1bf021290e6241331fc5a3c98e2901
Timestamp: 1704387099 Timestamp [UCT]: 2024-01-04 16:51:39 Age [y:d:h:m:s]: 01:087:23:06:02
Block: 928125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323945 RingCT/type: yes/0
Extra: 014823f3fe03772ec6fbbf188087d9863c1b1bf021290e6241331fc5a3c98e290102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f23766e540d9b5e41ecb67dafcfd46c4457fd856f6477a55aebb31bc6d785f2e 0.600000000000 1385981 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": 928135, "vin": [ { "gen": { "height": 928125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f23766e540d9b5e41ecb67dafcfd46c4457fd856f6477a55aebb31bc6d785f2e" } } ], "extra": [ 1, 72, 35, 243, 254, 3, 119, 46, 198, 251, 191, 24, 128, 135, 217, 134, 60, 27, 27, 240, 33, 41, 14, 98, 65, 51, 31, 197, 163, 201, 142, 41, 1, 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