Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd099ebc0fa5c3d610011cb90e6ee881587170476a2acb67fae9871be4f46e7

Tx prefix hash: b4b72202299625c4d8908dcaf27a71d5447be1ad48cf077e3fa230ea4312ded1
Tx public key: d44cb5c66bd267f433721c16a495f333fcdfd1a4ced704b2d5926601c313a144
Timestamp: 1674130999 Timestamp [UCT]: 2023-01-19 12:23:19 Age [y:d:h:m:s]: 02:081:06:05:48
Block: 678141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579734 RingCT/type: yes/0
Extra: 01d44cb5c66bd267f433721c16a495f333fcdfd1a4ced704b2d5926601c313a14402110000000152542ceb000000000000000000

1 output(s) for total of 3.475660134000 dcy

stealth address amount amount idx
00: 362e01eae928de33edeb3ceb3a26ce22d2c6338eb5c627035c8e6407d7c6156b 3.475660134000 1119974 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": 678151, "vin": [ { "gen": { "height": 678141 } } ], "vout": [ { "amount": 3475660134, "target": { "key": "362e01eae928de33edeb3ceb3a26ce22d2c6338eb5c627035c8e6407d7c6156b" } } ], "extra": [ 1, 212, 76, 181, 198, 107, 210, 103, 244, 51, 114, 28, 22, 164, 149, 243, 51, 252, 223, 209, 164, 206, 215, 4, 178, 213, 146, 102, 1, 195, 19, 161, 68, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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