Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 694ac0ff561fdf966be5cb4d80639753d97a208d9d37cc66bae2e1aa1f3eb1f0

Tx prefix hash: 1b9a6767fd6b443c82cac8f59466f6c96eb643efc61fb6438a916cb9d6b27ca8
Tx public key: 3e966ee78fa587e4cf779f5e63dfe7e9d869e24e2e5e80c78525f531301a728f
Timestamp: 1647892942 Timestamp [UCT]: 2022-03-21 20:02:22 Age [y:d:h:m:s]: 02:360:14:58:53
Block: 463456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 777049 RingCT/type: yes/0
Extra: 013e966ee78fa587e4cf779f5e63dfe7e9d869e24e2e5e80c78525f531301a728f021100000016bf7ee4e7000000000000000000

1 output(s) for total of 17.880437515000 dcy

stealth address amount amount idx
00: f7d2005294750d32d59ccfbbd2693984a9ae4cf4fbcffb07f9b24af97008cda5 17.880437515000 881127 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": 463466, "vin": [ { "gen": { "height": 463456 } } ], "vout": [ { "amount": 17880437515, "target": { "key": "f7d2005294750d32d59ccfbbd2693984a9ae4cf4fbcffb07f9b24af97008cda5" } } ], "extra": [ 1, 62, 150, 110, 231, 143, 165, 135, 228, 207, 119, 159, 94, 99, 223, 231, 233, 216, 105, 226, 78, 46, 94, 128, 199, 133, 37, 245, 49, 48, 26, 114, 143, 2, 17, 0, 0, 0, 22, 191, 126, 228, 231, 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