Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9447658607aabb4ae12e633273f843b8582f203cdcd52bdf410dd400db4a378c

Tx prefix hash: 8bf2bd14d02377c3c07c84e5c1aedfca5d77cae44001523164229955039846dc
Tx public key: 603786a8f2a10e752f149392bc05c900b04ae3e457d3abdbf353b1f479dd4f2a
Timestamp: 1724961308 Timestamp [UCT]: 2024-08-29 19:55:08 Age [y:d:h:m:s]: 00:132:10:00:21
Block: 1098680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94723 RingCT/type: yes/0
Extra: 01603786a8f2a10e752f149392bc05c900b04ae3e457d3abdbf353b1f479dd4f2a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d9347f9fedc9632be2f03308c9a0983cb6566b92e8b81b5173e422eea4b075f 0.600000000000 1574479 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": 1098690, "vin": [ { "gen": { "height": 1098680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d9347f9fedc9632be2f03308c9a0983cb6566b92e8b81b5173e422eea4b075f" } } ], "extra": [ 1, 96, 55, 134, 168, 242, 161, 14, 117, 47, 20, 147, 146, 188, 5, 201, 0, 176, 74, 227, 228, 87, 211, 171, 219, 243, 83, 177, 244, 121, 221, 79, 42, 2, 17, 0, 0, 0, 1, 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