Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 754de559e08484399b9cefa6aafff14c92148ac46f03425f8e0401eaec7fe7db

Tx prefix hash: 4b386cc2d281d3b5154aac2151ed55428a702fb27cfa6eb79a146cf766d257d0
Tx public key: f63cb0a064bd61d526aab0450aa770a14afb39767f2829527ba56f5216ca3e1d
Timestamp: 1704041754 Timestamp [UCT]: 2023-12-31 16:55:54 Age [y:d:h:m:s]: 00:358:21:10:11
Block: 925254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256958 RingCT/type: yes/0
Extra: 01f63cb0a064bd61d526aab0450aa770a14afb39767f2829527ba56f5216ca3e1d0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b62e0bc592d7d9c02c5799a50430f2361c47ae32e812fa2d4a0b57c74bd0c31 0.600000000000 1383014 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": 925264, "vin": [ { "gen": { "height": 925254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b62e0bc592d7d9c02c5799a50430f2361c47ae32e812fa2d4a0b57c74bd0c31" } } ], "extra": [ 1, 246, 60, 176, 160, 100, 189, 97, 213, 38, 170, 176, 69, 10, 167, 112, 161, 74, 251, 57, 118, 127, 40, 41, 82, 123, 165, 111, 82, 22, 202, 62, 29, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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