Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc303623c6ac40a17337e92eb93472390feafb98cb7ab1c37350589b7978a97b

Tx prefix hash: ba1fa655142bb68d49356d8c5bc71b91363b5cc6da142afe413efacb795210a3
Tx public key: ccdebafeb6bf39f072cd1205d887dbf42b4499d30001e3ea7ab1cb813e3b6fc3
Timestamp: 1702486696 Timestamp [UCT]: 2023-12-13 16:58:16 Age [y:d:h:m:s]: 01:038:18:18:11
Block: 912372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289008 RingCT/type: yes/0
Extra: 01ccdebafeb6bf39f072cd1205d887dbf42b4499d30001e3ea7ab1cb813e3b6fc3021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b3f48f7e3d6daf21d4a24058d6b8b8afc1a29c8243dbe2ccfc8e39dd0c820e 0.600000000000 1369598 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": 912382, "vin": [ { "gen": { "height": 912372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b3f48f7e3d6daf21d4a24058d6b8b8afc1a29c8243dbe2ccfc8e39dd0c820e" } } ], "extra": [ 1, 204, 222, 186, 254, 182, 191, 57, 240, 114, 205, 18, 5, 216, 135, 219, 244, 43, 68, 153, 211, 0, 1, 227, 234, 122, 177, 203, 129, 62, 59, 111, 195, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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