Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71adaf173042d968db36cca5e856dae843dc6badc550aa11f2aaf5fd28542c0a

Tx prefix hash: 50657136abd770e69cdb394a2557a347ab4ec58479474d64edb0fe68eccb6f2c
Tx public key: 4b56cb4351a88b772dd5a87ebdb45777040e6650efffc67f35ecb4b4c276f5b3
Timestamp: 1721946431 Timestamp [UCT]: 2024-07-25 22:27:11 Age [y:d:h:m:s]: 01:167:18:58:09
Block: 1073689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378503 RingCT/type: yes/0
Extra: 014b56cb4351a88b772dd5a87ebdb45777040e6650efffc67f35ecb4b4c276f5b3021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fb033bae8e714d17e5b8b6e38dae7e4161bdf7ce5b33a80aee0d17635458fa5 0.600000000000 1546196 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": 1073699, "vin": [ { "gen": { "height": 1073689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fb033bae8e714d17e5b8b6e38dae7e4161bdf7ce5b33a80aee0d17635458fa5" } } ], "extra": [ 1, 75, 86, 203, 67, 81, 168, 139, 119, 45, 213, 168, 126, 189, 180, 87, 119, 4, 14, 102, 80, 239, 255, 198, 127, 53, 236, 180, 180, 194, 118, 245, 179, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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