Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c9dbb6849c78fbb5e3ac620ef556abe65167cf010aed0c024a62e8720ecd3c

Tx prefix hash: 1dd5513d455486edbb7df5d147c128728eae78f8d7abae19734195d803ba7e11
Tx public key: fa64874f879333720913bed229407c32c0d57b62ff1d2469373abf3a2800c8b8
Timestamp: 1665562329 Timestamp [UCT]: 2022-10-12 08:12:09 Age [y:d:h:m:s]: 02:173:08:57:46
Block: 607377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645454 RingCT/type: yes/0
Extra: 01fa64874f879333720913bed229407c32c0d57b62ff1d2469373abf3a2800c8b8021100000020e7ace25d000000000000000000

1 output(s) for total of 5.963591867000 dcy

stealth address amount amount idx
00: 2a35fa0b85422c8ddcb8240c8a837dfba5f81511ad0f89fad726cc09b8ea5e0e 5.963591867000 1044005 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": 607387, "vin": [ { "gen": { "height": 607377 } } ], "vout": [ { "amount": 5963591867, "target": { "key": "2a35fa0b85422c8ddcb8240c8a837dfba5f81511ad0f89fad726cc09b8ea5e0e" } } ], "extra": [ 1, 250, 100, 135, 79, 135, 147, 51, 114, 9, 19, 190, 210, 41, 64, 124, 50, 192, 213, 123, 98, 255, 29, 36, 105, 55, 58, 191, 58, 40, 0, 200, 184, 2, 17, 0, 0, 0, 32, 231, 172, 226, 93, 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