Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3951fe7ce20174211fc8abfbd3d879cc15c1a5a74aeef4e2085a7a50c83bda

Tx prefix hash: fc755686a196684e397d5d4cda4c8904d27006d2a7281022c8d22b7cad567e8f
Tx public key: cf71a5488f9d26358957d7ee840db1c07d8af0fdece202f843facf69002d9fb2
Timestamp: 1576425595 Timestamp [UCT]: 2019-12-15 15:59:55 Age [y:d:h:m:s]: 05:321:00:41:23
Block: 27554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1373782 RingCT/type: yes/0
Extra: 01cf71a5488f9d26358957d7ee840db1c07d8af0fdece202f843facf69002d9fb202110000000aad433a0b000000000000000000

1 output(s) for total of 497.396844378000 dcy

stealth address amount amount idx
00: 66a1f19e8b69f808f12f47f082b1c4fb0a5b4610d370c3485d557e264d060710 497.396844378000 45566 of 0

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": 27564, "vin": [ { "gen": { "height": 27554 } } ], "vout": [ { "amount": 497396844378, "target": { "key": "66a1f19e8b69f808f12f47f082b1c4fb0a5b4610d370c3485d557e264d060710" } } ], "extra": [ 1, 207, 113, 165, 72, 143, 157, 38, 53, 137, 87, 215, 238, 132, 13, 177, 192, 125, 138, 240, 253, 236, 226, 2, 248, 67, 250, 207, 105, 0, 45, 159, 178, 2, 17, 0, 0, 0, 10, 173, 67, 58, 11, 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