Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86f8bd9293736f10b4453577bc570b80604df6516a00e209f359dee62d126b7f

Tx prefix hash: def6d54033fee03d6e5b48056da72e930d7c283f814d4fcb74fc39f91e1fa7e0
Tx public key: 5bbf9682d780cc78ef92f567db1d114c5cf5a182ce7f46c7883fa65223ae7bb9
Timestamp: 1724285148 Timestamp [UCT]: 2024-08-22 00:05:48 Age [y:d:h:m:s]: 01:074:08:03:19
Block: 1093088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311574 RingCT/type: yes/0
Extra: 015bbf9682d780cc78ef92f567db1d114c5cf5a182ce7f46c7883fa65223ae7bb9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be4ab1fba86eb7bf00b4aefd98d728cc4d73ead843ab11f0252e5d7bc80a6ec 0.600000000000 1567961 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": 1093098, "vin": [ { "gen": { "height": 1093088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be4ab1fba86eb7bf00b4aefd98d728cc4d73ead843ab11f0252e5d7bc80a6ec" } } ], "extra": [ 1, 91, 191, 150, 130, 215, 128, 204, 120, 239, 146, 245, 103, 219, 29, 17, 76, 92, 245, 161, 130, 206, 127, 70, 199, 136, 63, 166, 82, 35, 174, 123, 185, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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