Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f803dda711eb7ea389d6661806c899fe84bd99b9b22ecf154df9e792501d43c

Tx prefix hash: 0c5a940a5700c7e7148c7956310f2245048d387afc62c80a0a132de50425b116
Tx public key: e71db7750d2011a3cc8a3c9d0f04ffdbd5bdd0994557f82cc10cfa0df9670436
Timestamp: 1735409227 Timestamp [UCT]: 2024-12-28 18:07:07 Age [y:d:h:m:s]: 00:172:06:30:36
Block: 1185174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122834 RingCT/type: yes/0
Extra: 01e71db7750d2011a3cc8a3c9d0f04ffdbd5bdd0994557f82cc10cfa0df967043602110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc8c6ce5dde87d4749b455853277b3c0ff4932b2d4c4acc725f37514c97d3b75 0.600000000000 1671639 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": 1185184, "vin": [ { "gen": { "height": 1185174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc8c6ce5dde87d4749b455853277b3c0ff4932b2d4c4acc725f37514c97d3b75" } } ], "extra": [ 1, 231, 29, 183, 117, 13, 32, 17, 163, 204, 138, 60, 157, 15, 4, 255, 219, 213, 189, 208, 153, 69, 87, 248, 44, 193, 12, 250, 13, 249, 103, 4, 54, 2, 17, 0, 0, 0, 12, 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