Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35073e141cb25953efda7156d453f3c3c12f856f5a79aee19108d9b00666fc44

Tx prefix hash: 655a79e0ca73b69b05fc000c1fe5450817bfbe7e15bf7b9a07c19ff3fee5316b
Tx public key: c371291a153c76afb10a00c5ebd1b64628ae9d06fe38dc21bfdbfdeb778e0731
Timestamp: 1709712644 Timestamp [UCT]: 2024-03-06 08:10:44 Age [y:d:h:m:s]: 01:249:00:12:20
Block: 972283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436677 RingCT/type: yes/0
Extra: 01c371291a153c76afb10a00c5ebd1b64628ae9d06fe38dc21bfdbfdeb778e073102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22863ea75842e0810a76b9300f58f6abc5e0eccb76b5f8fa9c410e0bcd6b8bf9 0.600000000000 1432192 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": 972293, "vin": [ { "gen": { "height": 972283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22863ea75842e0810a76b9300f58f6abc5e0eccb76b5f8fa9c410e0bcd6b8bf9" } } ], "extra": [ 1, 195, 113, 41, 26, 21, 60, 118, 175, 177, 10, 0, 197, 235, 209, 182, 70, 40, 174, 157, 6, 254, 56, 220, 33, 191, 219, 253, 235, 119, 142, 7, 49, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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