Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbcdf9310dc603f67ffc7bfe01901a1de88e878380e34ed4dc518ec576fb3c3a

Tx prefix hash: 3c2bf7e0b84213193b7062ab92e2fe7c30402c4871125ef7396612ef83f1a5f7
Tx public key: 430ef145ea15f4588feef41f021ca11ce3e8c8c398f7de9d9a17631054740f8d
Timestamp: 1695981483 Timestamp [UCT]: 2023-09-29 09:58:03 Age [y:d:h:m:s]: 01:110:07:18:20
Block: 858636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340106 RingCT/type: yes/0
Extra: 01430ef145ea15f4588feef41f021ca11ce3e8c8c398f7de9d9a17631054740f8d02110000000a4b8f5122000000000000000000

1 output(s) for total of 0.876965562000 dcy

stealth address amount amount idx
00: 99dc83ff4eb0299e5b561cd4a24382091a810643089114fb436cd51405e60e59 0.876965562000 1312820 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": 858646, "vin": [ { "gen": { "height": 858636 } } ], "vout": [ { "amount": 876965562, "target": { "key": "99dc83ff4eb0299e5b561cd4a24382091a810643089114fb436cd51405e60e59" } } ], "extra": [ 1, 67, 14, 241, 69, 234, 21, 244, 88, 143, 238, 244, 31, 2, 28, 161, 28, 227, 232, 200, 195, 152, 247, 222, 157, 154, 23, 99, 16, 84, 116, 15, 141, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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