Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66daa748852111dd4e72c07681c606d2cf063bd1839f769e2c1942326781054b

Tx prefix hash: 42605e6c111385a7e11e28d8e17b0a49d2fa4136e4829ba5f137185964f15acb
Tx public key: 6ff8e9aaf3d0f4f167516cbb7cb458725bfe7abd3030d4d8b94a31338f6ef9a2
Timestamp: 1713867108 Timestamp [UCT]: 2024-04-23 10:11:48 Age [y:d:h:m:s]: 00:204:00:54:03
Block: 1006714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146059 RingCT/type: yes/0
Extra: 016ff8e9aaf3d0f4f167516cbb7cb458725bfe7abd3030d4d8b94a31338f6ef9a20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63664b286f9861a685f6a4c7508d1b3664649e1fdbf0a7185f50d4d9031e6d32 0.600000000000 1467828 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": 1006724, "vin": [ { "gen": { "height": 1006714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63664b286f9861a685f6a4c7508d1b3664649e1fdbf0a7185f50d4d9031e6d32" } } ], "extra": [ 1, 111, 248, 233, 170, 243, 208, 244, 241, 103, 81, 108, 187, 124, 180, 88, 114, 91, 254, 122, 189, 48, 48, 212, 216, 185, 74, 49, 51, 143, 110, 249, 162, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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