Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30faff3387d0f70efc822556fe38f2567a8ff42da3dd849e001efe0e18cc6d54

Tx prefix hash: 02a5e4a3808c487d4364df9be0aafdb0efcfba43522533321fe4360748c3d9fc
Tx public key: 8d88d1a6f521c963e04351bcc80e3f4a0cd456969ff9d757a88b8d16d0c5a591
Timestamp: 1724738653 Timestamp [UCT]: 2024-08-27 06:04:13 Age [y:d:h:m:s]: 00:224:23:36:59
Block: 1096829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160662 RingCT/type: yes/0
Extra: 018d88d1a6f521c963e04351bcc80e3f4a0cd456969ff9d757a88b8d16d0c5a591021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e338b30bfc6fd19b4763dd0f812a2f370debbc42e6a608c760a549472fc21db9 0.600000000000 1572024 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": 1096839, "vin": [ { "gen": { "height": 1096829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e338b30bfc6fd19b4763dd0f812a2f370debbc42e6a608c760a549472fc21db9" } } ], "extra": [ 1, 141, 136, 209, 166, 245, 33, 201, 99, 224, 67, 81, 188, 200, 14, 63, 74, 12, 212, 86, 150, 159, 249, 215, 87, 168, 139, 141, 22, 208, 197, 165, 145, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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