Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858fa85b1ea2e43b6b6ad757e55e99ea1706359b81987493da4469c166a5c441

Tx prefix hash: 4cb1a8760b060e8de13586b182f3367e604a45e13951023110fbead06d64d9f4
Tx public key: 42d5ac8add420a5e5c103448f80442b66a68cd14d0addad3236acf13e52a9bf2
Timestamp: 1679971869 Timestamp [UCT]: 2023-03-28 02:51:09 Age [y:d:h:m:s]: 02:001:06:57:52
Block: 726604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522430 RingCT/type: yes/0
Extra: 0142d5ac8add420a5e5c103448f80442b66a68cd14d0addad3236acf13e52a9bf2021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.401372638000 dcy

stealth address amount amount idx
00: 289ce80a737754b28f5471af1c2be42fc6ae5fd41e18a24199a0c8b9ab21198b 2.401372638000 1171849 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": 726614, "vin": [ { "gen": { "height": 726604 } } ], "vout": [ { "amount": 2401372638, "target": { "key": "289ce80a737754b28f5471af1c2be42fc6ae5fd41e18a24199a0c8b9ab21198b" } } ], "extra": [ 1, 66, 213, 172, 138, 221, 66, 10, 94, 92, 16, 52, 72, 248, 4, 66, 182, 106, 104, 205, 20, 208, 173, 218, 211, 35, 106, 207, 19, 229, 42, 155, 242, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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