Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 670aac852ebf9f124b0bb52be279066dcde097edc8edc6f59778f1a3bd69731e

Tx prefix hash: aa5e63ab50ec2574b7cc0097bd5ce29442c299ad3b696870e1137db9b6e7b6d3
Tx public key: 23fd986632761dcca5c5a27f79e1c48a3aef3a8255d83d0804f68655b3974b6f
Timestamp: 1705057353 Timestamp [UCT]: 2024-01-12 11:02:33 Age [y:d:h:m:s]: 01:067:08:32:05
Block: 933658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309258 RingCT/type: yes/0
Extra: 0123fd986632761dcca5c5a27f79e1c48a3aef3a8255d83d0804f68655b3974b6f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26e6c4a669289a334b2238dbd3397b5753ea5e600cc3fd42009223fc6633c2b3 0.600000000000 1391628 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": 933668, "vin": [ { "gen": { "height": 933658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26e6c4a669289a334b2238dbd3397b5753ea5e600cc3fd42009223fc6633c2b3" } } ], "extra": [ 1, 35, 253, 152, 102, 50, 118, 29, 204, 165, 197, 162, 127, 121, 225, 196, 138, 58, 239, 58, 130, 85, 216, 61, 8, 4, 246, 134, 85, 179, 151, 75, 111, 2, 17, 0, 0, 0, 1, 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