Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1321476abbb9c8a6171f196a1c68ef9f35f166af0ce37f2479c003b254429476

Tx prefix hash: b0b551dee17d9d17f6b70fd1068ba07ae17ed4536130241e6ecab20d3076881e
Tx public key: a19cb0ec8ae01a05bb1c2bdfe5ab078cbe5c22ed50409cad7eedb59ea1728b9b
Timestamp: 1704885913 Timestamp [UCT]: 2024-01-10 11:25:13 Age [y:d:h:m:s]: 01:363:03:37:44
Block: 932244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518450 RingCT/type: yes/0
Extra: 01a19cb0ec8ae01a05bb1c2bdfe5ab078cbe5c22ed50409cad7eedb59ea1728b9b0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 848efb561fd4e133bad6cb69fc21e1eab597c0fbec58bb4e7399cbce8184d446 0.600000000000 1390174 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": 932254, "vin": [ { "gen": { "height": 932244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "848efb561fd4e133bad6cb69fc21e1eab597c0fbec58bb4e7399cbce8184d446" } } ], "extra": [ 1, 161, 156, 176, 236, 138, 224, 26, 5, 187, 28, 43, 223, 229, 171, 7, 140, 190, 92, 34, 237, 80, 64, 156, 173, 126, 237, 181, 158, 161, 114, 139, 155, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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