Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb996e315effe1b46d5d0273be06d49ade128bfd1783d63ba01f717cf6a1e030

Tx prefix hash: 544d78df818a790de21972e621ffd5e8fc2477b1b8265ddc22ac8a512ce51c5e
Tx public key: f2d1fd636429c38592ac4f8a27f76975fd963ca04828902c37996ca1cf2b3353
Timestamp: 1581231658 Timestamp [UCT]: 2020-02-09 07:00:58 Age [y:d:h:m:s]: 04:270:22:35:11
Block: 61092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1085786 RingCT/type: yes/0
Extra: 01f2d1fd636429c38592ac4f8a27f76975fd963ca04828902c37996ca1cf2b33530211000000084943cd9f000000000000000000

1 output(s) for total of 385.103672491000 dcy

stealth address amount amount idx
00: 350c97d67d9d7903df72bc82e82aea587f15804c376ab9694eca56bff6beb29e 385.103672491000 112599 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": 61102, "vin": [ { "gen": { "height": 61092 } } ], "vout": [ { "amount": 385103672491, "target": { "key": "350c97d67d9d7903df72bc82e82aea587f15804c376ab9694eca56bff6beb29e" } } ], "extra": [ 1, 242, 209, 253, 99, 100, 41, 195, 133, 146, 172, 79, 138, 39, 247, 105, 117, 253, 150, 60, 160, 72, 40, 144, 44, 55, 153, 108, 161, 207, 43, 51, 83, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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