Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c9618beb8197b25c7807b15a3fd610478df8c1483405f5f3938fe1dba27410

Tx prefix hash: 598f38a4f3318463572a40823df2b3c8c5f665d6cc1988cdf9e3ff2ed42742d4
Tx public key: c3323a36e108b7dcdcd045ecfab8a167263beac8a60512ffb4a9a0511f4e0245
Timestamp: 1718298171 Timestamp [UCT]: 2024-06-13 17:02:51 Age [y:d:h:m:s]: 00:254:17:33:23
Block: 1043448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181994 RingCT/type: yes/0
Extra: 01c3323a36e108b7dcdcd045ecfab8a167263beac8a60512ffb4a9a0511f4e024502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be543d54e98e40d22d0c3d00b2fb0c2f22ec02e9029213609935967a2a8e9797 0.600000000000 1512601 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": 1043458, "vin": [ { "gen": { "height": 1043448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be543d54e98e40d22d0c3d00b2fb0c2f22ec02e9029213609935967a2a8e9797" } } ], "extra": [ 1, 195, 50, 58, 54, 225, 8, 183, 220, 220, 208, 69, 236, 250, 184, 161, 103, 38, 59, 234, 200, 166, 5, 18, 255, 180, 169, 160, 81, 31, 78, 2, 69, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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