Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 836ab4c8acd4ad8c2f28f8c0d45113a4efb456ef1cb645bef831d3caae0bc32a

Tx prefix hash: 7a4d403b8e676c22b574518f7735ca5b97ab487a17c001450976a989374649e9
Tx public key: 7ca81f4ee2fe78a4526c7602a9bf782ac64b8d85b6446c9bd1ac7ba36d589d73
Timestamp: 1722417215 Timestamp [UCT]: 2024-07-31 09:13:35 Age [y:d:h:m:s]: 00:268:02:30:27
Block: 1077594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191535 RingCT/type: yes/0
Extra: 017ca81f4ee2fe78a4526c7602a9bf782ac64b8d85b6446c9bd1ac7ba36d589d7302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77d97343a37a42453023349d35f949404db06cf86bbc143cb0d99cb190a0bd9 0.600000000000 1550145 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": 1077604, "vin": [ { "gen": { "height": 1077594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77d97343a37a42453023349d35f949404db06cf86bbc143cb0d99cb190a0bd9" } } ], "extra": [ 1, 124, 168, 31, 78, 226, 254, 120, 164, 82, 108, 118, 2, 169, 191, 120, 42, 198, 75, 141, 133, 182, 68, 108, 155, 209, 172, 123, 163, 109, 88, 157, 115, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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