Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd012ccc55273c3626fb36b4b531696d18ae8cdc20bbceb74af9da708d0137b

Tx prefix hash: 4320795d3675077c333e5b357450723d7e9013089275cea29e596fc3a2370084
Tx public key: 873f09dc164f2dffd3ae83ac1fb9a7646e599311d11fba464f313c761a0969c4
Timestamp: 1710194639 Timestamp [UCT]: 2024-03-11 22:03:59 Age [y:d:h:m:s]: 01:241:21:59:57
Block: 976275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431596 RingCT/type: yes/0
Extra: 01873f09dc164f2dffd3ae83ac1fb9a7646e599311d11fba464f313c761a0969c402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48e48d52f185d069c20a6ed6271d8bd091b5d0ad6adae7af71ab1c03d49ffa00 0.600000000000 1436266 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": 976285, "vin": [ { "gen": { "height": 976275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48e48d52f185d069c20a6ed6271d8bd091b5d0ad6adae7af71ab1c03d49ffa00" } } ], "extra": [ 1, 135, 63, 9, 220, 22, 79, 45, 255, 211, 174, 131, 172, 31, 185, 167, 100, 110, 89, 147, 17, 209, 31, 186, 70, 79, 49, 60, 118, 26, 9, 105, 196, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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