Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484df7fa9d7814b5a9797da6d450c5f670a2d0c39f61bfcf3852bedd515828e2

Tx prefix hash: 4ce5b3bd8e5b0eedd2877632af2d736b1c9162e3d847d864dab3284c8d073df1
Tx public key: 50a449a4f48d87a878bbec2ed526a24fde860e86e8778e73a99b3d27765656c0
Timestamp: 1729919005 Timestamp [UCT]: 2024-10-26 05:03:25 Age [y:d:h:m:s]: 00:029:02:49:41
Block: 1139758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20792 RingCT/type: yes/0
Extra: 0150a449a4f48d87a878bbec2ed526a24fde860e86e8778e73a99b3d27765656c00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19cbd00f3db39d5d5b1b0eb497d78c814c70560ced4b10500511a0253fb1ced8 0.600000000000 1623545 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": 1139768, "vin": [ { "gen": { "height": 1139758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19cbd00f3db39d5d5b1b0eb497d78c814c70560ced4b10500511a0253fb1ced8" } } ], "extra": [ 1, 80, 164, 73, 164, 244, 141, 135, 168, 120, 187, 236, 46, 213, 38, 162, 79, 222, 134, 14, 134, 232, 119, 142, 115, 169, 155, 61, 39, 118, 86, 86, 192, 2, 17, 0, 0, 0, 1, 31, 10, 83, 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