Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ee123d8973f4517d8a7b144c6f53ebb07d41b2914996a1e04d8c939581346e5

Tx prefix hash: 83ba5d9951a6bedc5bc0d479570c71db489abd541467aae32dd8c609c9933863
Tx public key: 0dcf4f2f8523c9ebb07cf751ba0b166e97e61538759d294d25304dd01168045c
Timestamp: 1578839081 Timestamp [UCT]: 2020-01-12 14:24:41 Age [y:d:h:m:s]: 05:297:15:34:23
Block: 44033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360558 RingCT/type: yes/0
Extra: 010dcf4f2f8523c9ebb07cf751ba0b166e97e61538759d294d25304dd01168045c0211000000128a2ee0d9000000000000000000

1 output(s) for total of 438.632930906000 dcy

stealth address amount amount idx
00: 6564dc28f8fb8771be7cb24b5e4926c3de73fdd4e036d9ad6df572de5aaf0fcd 438.632930906000 79992 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": 44043, "vin": [ { "gen": { "height": 44033 } } ], "vout": [ { "amount": 438632930906, "target": { "key": "6564dc28f8fb8771be7cb24b5e4926c3de73fdd4e036d9ad6df572de5aaf0fcd" } } ], "extra": [ 1, 13, 207, 79, 47, 133, 35, 201, 235, 176, 124, 247, 81, 186, 11, 22, 110, 151, 230, 21, 56, 117, 157, 41, 77, 37, 48, 77, 208, 17, 104, 4, 92, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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