Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb95aa351c5f7c5e4576336ca91b56f5ff132c6ddb0c26c9820f9d089300f05

Tx prefix hash: 987bcdd1278fda3b134351a448d582c84c518b015900bb61b3be09b61cb6672c
Tx public key: 628c0c41535d7f0feebb5dd3de656859edde217458324066b136b7e35b5528d1
Timestamp: 1730530455 Timestamp [UCT]: 2024-11-02 06:54:15 Age [y:d:h:m:s]: 00:139:16:27:54
Block: 1144768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99668 RingCT/type: yes/0
Extra: 01628c0c41535d7f0feebb5dd3de656859edde217458324066b136b7e35b5528d10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32d943fcab059cb07a4734c136d54cac0efa7d5ea2b7c26767e15f5e3090910a 0.600000000000 1629071 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": 1144778, "vin": [ { "gen": { "height": 1144768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32d943fcab059cb07a4734c136d54cac0efa7d5ea2b7c26767e15f5e3090910a" } } ], "extra": [ 1, 98, 140, 12, 65, 83, 93, 127, 15, 238, 187, 93, 211, 222, 101, 104, 89, 237, 222, 33, 116, 88, 50, 64, 102, 177, 54, 183, 227, 91, 85, 40, 209, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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