Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f6d82f9686031101b27b1a44a7d583be44b5c080060118eaccfbed77c0d955f

Tx prefix hash: 5f120b5fbdb36752c60241e7bf0ca606d552d8a6b450ee9df7fb28a1c5232c93
Tx public key: 83c99e3f4723e514c71a2c003860ecf5c9580a344f10944e4256623b9dc387e7
Timestamp: 1714806353 Timestamp [UCT]: 2024-05-04 07:05:53 Age [y:d:h:m:s]: 00:194:02:13:20
Block: 1014504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138928 RingCT/type: yes/0
Extra: 0183c99e3f4723e514c71a2c003860ecf5c9580a344f10944e4256623b9dc387e70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81cd2840e1f542247f8475865ab49d49477f4da4b5151b4ae84c390eb0fe2f07 0.600000000000 1477613 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": 1014514, "vin": [ { "gen": { "height": 1014504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81cd2840e1f542247f8475865ab49d49477f4da4b5151b4ae84c390eb0fe2f07" } } ], "extra": [ 1, 131, 201, 158, 63, 71, 35, 229, 20, 199, 26, 44, 0, 56, 96, 236, 245, 201, 88, 10, 52, 79, 16, 148, 78, 66, 86, 98, 59, 157, 195, 135, 231, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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