Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a696a1b1ac05509df0b156836519671ed66803e33191b18d0da6789281e247c

Tx prefix hash: e0f40cdf206fd64b2e40f67f3714c44c001c7f60dc4e6bb415a4e7d811025b9e
Tx public key: 895b335d7b796852b69fa77b405ffe93b95d3406fee62147e47c1070080fbc47
Timestamp: 1727390851 Timestamp [UCT]: 2024-09-26 22:47:31 Age [y:d:h:m:s]: 00:226:18:36:55
Block: 1118826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161911 RingCT/type: yes/0
Extra: 01895b335d7b796852b69fa77b405ffe93b95d3406fee62147e47c1070080fbc4702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73e90d5cf7e3b5884f37482a2bc83e013f940b941dc6c1fea0a39ea5a0bdbec2 0.600000000000 1600155 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": 1118836, "vin": [ { "gen": { "height": 1118826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73e90d5cf7e3b5884f37482a2bc83e013f940b941dc6c1fea0a39ea5a0bdbec2" } } ], "extra": [ 1, 137, 91, 51, 93, 123, 121, 104, 82, 182, 159, 167, 123, 64, 95, 254, 147, 185, 93, 52, 6, 254, 230, 33, 71, 228, 124, 16, 112, 8, 15, 188, 71, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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