Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646a821d1b20fab3fe68de22739a4b615e41c745d50af72de39cd332b612d660

Tx prefix hash: 8871f01cab5058bce88b39080d2804cc8dc35c2d34e57dc510502eb6c620c47e
Tx public key: 750212c41c6f0e90a2eb2a05d182bb5332c2430e757a66671dfa422f42399494
Timestamp: 1700811750 Timestamp [UCT]: 2023-11-24 07:42:30 Age [y:d:h:m:s]: 01:057:20:27:42
Block: 898474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302700 RingCT/type: yes/0
Extra: 01750212c41c6f0e90a2eb2a05d182bb5332c2430e757a66671dfa422f423994940211000000024b8f5122000000000000000000

1 output(s) for total of 0.647116762000 dcy

stealth address amount amount idx
00: d282ebf7a598cfc5b2f54d00e79fc70327c5104ac513d18a38f1bb581598d125 0.647116762000 1354891 of 0

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": 898484, "vin": [ { "gen": { "height": 898474 } } ], "vout": [ { "amount": 647116762, "target": { "key": "d282ebf7a598cfc5b2f54d00e79fc70327c5104ac513d18a38f1bb581598d125" } } ], "extra": [ 1, 117, 2, 18, 196, 28, 111, 14, 144, 162, 235, 42, 5, 209, 130, 187, 83, 50, 194, 67, 14, 117, 122, 102, 103, 29, 250, 66, 47, 66, 57, 148, 148, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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