Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8bd1e59f72c698593bbe53efb9ddc587b1c7285a97aa377f0819efaa30d8986

Tx prefix hash: fcb79d3571024f6d68b45b646a43129ba4c1d69778ef94796769ec7868efd3a0
Tx public key: e93566afa3ca57b9715d34c9c892aa1afd4658398ddaeb77f7c035b8640a91c3
Timestamp: 1721516338 Timestamp [UCT]: 2024-07-20 22:58:58 Age [y:d:h:m:s]: 00:244:01:53:32
Block: 1070122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174363 RingCT/type: yes/0
Extra: 01e93566afa3ca57b9715d34c9c892aa1afd4658398ddaeb77f7c035b8640a91c30211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ad2e3e3a06dab1e4b2c07a8f1705c983b193d9d6df2fe50fdd96d27b4523e6 0.600000000000 1541825 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": 1070132, "vin": [ { "gen": { "height": 1070122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ad2e3e3a06dab1e4b2c07a8f1705c983b193d9d6df2fe50fdd96d27b4523e6" } } ], "extra": [ 1, 233, 53, 102, 175, 163, 202, 87, 185, 113, 93, 52, 201, 200, 146, 170, 26, 253, 70, 88, 57, 141, 218, 235, 119, 247, 192, 53, 184, 100, 10, 145, 195, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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