Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8ebf6dc6ac76cdf827e37bd0ebcaae1533154b43f46c6e562e6752dc79be541

Tx prefix hash: f9b41ce8980d27d2ee592f6da691cfb3f901e09c88b3042260abed9370439e22
Tx public key: f2278a34ebd362353387e79878a6be969089f021a711dd1c1afdecf2e9109ebe
Timestamp: 1715601521 Timestamp [UCT]: 2024-05-13 11:58:41 Age [y:d:h:m:s]: 01:177:00:42:45
Block: 1021115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385089 RingCT/type: yes/0
Extra: 01f2278a34ebd362353387e79878a6be969089f021a711dd1c1afdecf2e9109ebe02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 154ba758503aa2ff30a3c48e2bfe0b1b3af1fc2b7750858f0b9d7f5f22adfe71 0.600000000000 1485328 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": 1021125, "vin": [ { "gen": { "height": 1021115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "154ba758503aa2ff30a3c48e2bfe0b1b3af1fc2b7750858f0b9d7f5f22adfe71" } } ], "extra": [ 1, 242, 39, 138, 52, 235, 211, 98, 53, 51, 135, 231, 152, 120, 166, 190, 150, 144, 137, 240, 33, 167, 17, 221, 28, 26, 253, 236, 242, 233, 16, 158, 190, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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