Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834a3f34d46f054989832ef022f423ea3ee6b49f1e0398f748e8e67bb9b5be8f

Tx prefix hash: a0beb68fe96881471fa9c77ca1a378d53f6c60bc6c431eb6a62b41be36c356cb
Tx public key: 834ab970476ea29f72a25c405e61febc6870a2d8fc6eee3f3fb46c2c9fec18bf
Timestamp: 1701816270 Timestamp [UCT]: 2023-12-05 22:44:30 Age [y:d:h:m:s]: 01:120:08:59:30
Block: 906807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347173 RingCT/type: yes/0
Extra: 01834ab970476ea29f72a25c405e61febc6870a2d8fc6eee3f3fb46c2c9fec18bf02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.607256188000 dcy

stealth address amount amount idx
00: c6d7ed1196cbd5a1d940576f644798a11f9d1f24e23c550c2ac21476a7b32ee0 0.607256188000 1363766 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": 906817, "vin": [ { "gen": { "height": 906807 } } ], "vout": [ { "amount": 607256188, "target": { "key": "c6d7ed1196cbd5a1d940576f644798a11f9d1f24e23c550c2ac21476a7b32ee0" } } ], "extra": [ 1, 131, 74, 185, 112, 71, 110, 162, 159, 114, 162, 92, 64, 94, 97, 254, 188, 104, 112, 162, 216, 252, 110, 238, 63, 63, 180, 108, 44, 159, 236, 24, 191, 2, 17, 0, 0, 0, 13, 230, 210, 127, 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