Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b46cd88508ac795fd54ebbada0e11a25b1dc5c8c0a85a5d4f1971d71ec93fb99

Tx prefix hash: 6e2a3228055564af12aca40a1d27f873ef8e69a1f0e99a1faddea34165977252
Tx public key: 614a6b0068010e8bc679f83b19830eba7c4cb85b4d40cf0dd1ed9a79d732faa1
Timestamp: 1696459762 Timestamp [UCT]: 2023-10-04 22:49:22 Age [y:d:h:m:s]: 01:172:12:17:14
Block: 862594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384339 RingCT/type: yes/0
Extra: 01614a6b0068010e8bc679f83b19830eba7c4cb85b4d40cf0dd1ed9a79d732faa1021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.850879453000 dcy

stealth address amount amount idx
00: e5f55666377e6454104ec65d53fd37653260c363fc53f9e2da623b47c8234285 0.850879453000 1317022 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": 862604, "vin": [ { "gen": { "height": 862594 } } ], "vout": [ { "amount": 850879453, "target": { "key": "e5f55666377e6454104ec65d53fd37653260c363fc53f9e2da623b47c8234285" } } ], "extra": [ 1, 97, 74, 107, 0, 104, 1, 14, 139, 198, 121, 248, 59, 25, 131, 14, 186, 124, 76, 184, 91, 77, 64, 207, 13, 209, 237, 154, 121, 215, 50, 250, 161, 2, 17, 0, 0, 0, 5, 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