Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62a610e2bb886dd298cbd96682e1531e7197427d225726048c2daf12df684b34

Tx prefix hash: a4f8e59ac35a542f6fcbf68c337532a895d75cb79ebd942ed258e8f27b11f94d
Tx public key: 1c48c7e6d4da4835c4a081e09dd3575af11af1a4867c7ff795b4da383c7eba40
Timestamp: 1702321514 Timestamp [UCT]: 2023-12-11 19:05:14 Age [y:d:h:m:s]: 01:040:18:41:54
Block: 911000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290452 RingCT/type: yes/0
Extra: 011c48c7e6d4da4835c4a081e09dd3575af11af1a4867c7ff795b4da383c7eba40021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 658d9b0bf5ae20650a52399b5d3b8b0804fd551c35cf380ed5a48cd54b0e6501 0.600000000000 1368175 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": 911010, "vin": [ { "gen": { "height": 911000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "658d9b0bf5ae20650a52399b5d3b8b0804fd551c35cf380ed5a48cd54b0e6501" } } ], "extra": [ 1, 28, 72, 199, 230, 212, 218, 72, 53, 196, 160, 129, 224, 157, 211, 87, 90, 241, 26, 241, 164, 134, 124, 127, 247, 149, 180, 218, 56, 60, 126, 186, 64, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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