Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85ca12de7249807f0f8f14706f98886f1bc097356968cb4600abf2cf4c900845

Tx prefix hash: 5f1ac8a246bcdd6928f5519ae7114fcb48aaee38555ab72ac0f2880c155b6e34
Tx public key: a1e8901ab7adb6972b9f30224a5fef9c3746b1b1b789296aa252b6204c9625f5
Timestamp: 1718077503 Timestamp [UCT]: 2024-06-11 03:45:03 Age [y:d:h:m:s]: 00:263:06:20:05
Block: 1041629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188095 RingCT/type: yes/0
Extra: 01a1e8901ab7adb6972b9f30224a5fef9c3746b1b1b789296aa252b6204c9625f50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e717e991d82bc4fd9dccda5ce455deebb6704fe9442e7b8944cdb18f8a590ecb 0.600000000000 1510350 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": 1041639, "vin": [ { "gen": { "height": 1041629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e717e991d82bc4fd9dccda5ce455deebb6704fe9442e7b8944cdb18f8a590ecb" } } ], "extra": [ 1, 161, 232, 144, 26, 183, 173, 182, 151, 43, 159, 48, 34, 74, 95, 239, 156, 55, 70, 177, 177, 183, 137, 41, 106, 162, 82, 182, 32, 76, 150, 37, 245, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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