Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08bbe8f81d1886f0244ebe2f95767d8fab5646db841b2aa056c9e2fa60fffa95

Tx prefix hash: a709a1d5511bdbceda1e99cefe3be177a1214e5fdbcd38a5d30cc9b5bb367fac
Tx public key: 1aeaf6c4bfe1aced9fa49f0b496132451217520983bd2458604db251688cf39a
Timestamp: 1670423819 Timestamp [UCT]: 2022-12-07 14:36:59 Age [y:d:h:m:s]: 02:044:06:10:44
Block: 647434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553517 RingCT/type: yes/0
Extra: 011aeaf6c4bfe1aced9fa49f0b496132451217520983bd2458604db251688cf39a021100000007faf35c9c000000000000000000

1 output(s) for total of 4.393214271000 dcy

stealth address amount amount idx
00: 0d68a8489dc2023394b7b7ee43fbc2c7750df79c3db3cddedc1d59a9c012f1eb 4.393214271000 1087707 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": 647444, "vin": [ { "gen": { "height": 647434 } } ], "vout": [ { "amount": 4393214271, "target": { "key": "0d68a8489dc2023394b7b7ee43fbc2c7750df79c3db3cddedc1d59a9c012f1eb" } } ], "extra": [ 1, 26, 234, 246, 196, 191, 225, 172, 237, 159, 164, 159, 11, 73, 97, 50, 69, 18, 23, 82, 9, 131, 189, 36, 88, 96, 77, 178, 81, 104, 140, 243, 154, 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