Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b968f2dacc22c0dae292bfa2265bc10ba91bd88a8fdbc12c5ecf5d5ef87c64f

Tx prefix hash: 031d5f9acb93db876309c42e507adf5a17793d309898823155f9718b0746a03b
Tx public key: fbef7a6514953cd7cf7516ffcef94d123c4aac9b2c23a8aa5a468be38e5dfa96
Timestamp: 1712571967 Timestamp [UCT]: 2024-04-08 10:26:07 Age [y:d:h:m:s]: 01:024:23:28:29
Block: 995944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278850 RingCT/type: yes/0
Extra: 01fbef7a6514953cd7cf7516ffcef94d123c4aac9b2c23a8aa5a468be38e5dfa9602110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21714309c53bda01a3ac7921c16ea41aa2db550f371cb28e7a0bd3136dd58676 0.600000000000 1456360 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": 995954, "vin": [ { "gen": { "height": 995944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21714309c53bda01a3ac7921c16ea41aa2db550f371cb28e7a0bd3136dd58676" } } ], "extra": [ 1, 251, 239, 122, 101, 20, 149, 60, 215, 207, 117, 22, 255, 206, 249, 77, 18, 60, 74, 172, 155, 44, 35, 168, 170, 90, 70, 139, 227, 142, 93, 250, 150, 2, 17, 0, 0, 0, 12, 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