Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4abaf419e8e4dbd53faeec0e43f812c84c432bf58823bf8dea7be0cdd68ef6a2

Tx prefix hash: de2ca79dc496215b8d0a8c7b02a29625f1d7f2e2084d0b3fbb1d4e9f82066032
Tx public key: dcf16e295e06a80ea44b2b4c644c8296ec2d62daee30e32b99892951789972cc
Timestamp: 1632144569 Timestamp [UCT]: 2021-09-20 13:29:29 Age [y:d:h:m:s]: 03:168:07:49:18
Block: 337573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896069 RingCT/type: yes/0
Extra: 01dcf16e295e06a80ea44b2b4c644c8296ec2d62daee30e32b99892951789972cc0211000000055410958b000000000000000000

1 output(s) for total of 46.717646212000 dcy

stealth address amount amount idx
00: df917ca6b45140e590c3a8c75396a29006cb3d707b065c67fb7e58c6e1a5f6e3 46.717646212000 695052 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": 337583, "vin": [ { "gen": { "height": 337573 } } ], "vout": [ { "amount": 46717646212, "target": { "key": "df917ca6b45140e590c3a8c75396a29006cb3d707b065c67fb7e58c6e1a5f6e3" } } ], "extra": [ 1, 220, 241, 110, 41, 94, 6, 168, 14, 164, 75, 43, 76, 100, 76, 130, 150, 236, 45, 98, 218, 238, 48, 227, 43, 153, 137, 41, 81, 120, 153, 114, 204, 2, 17, 0, 0, 0, 5, 84, 16, 149, 139, 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