Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d064badab1a673a8919186f141bebe31f03083ce31a08c7e4c2d60e21b52d74

Tx prefix hash: 1bc050396d1d19394fd83b5e83eee6adaf294ecf1ea8cfce3ee1136709840d65
Tx public key: 62e7645491f4a42aa4bc2e19b749a5c79456d2400d2a1d94559c0eeaeb861bb4
Timestamp: 1721725273 Timestamp [UCT]: 2024-07-23 09:01:13 Age [y:d:h:m:s]: 00:099:12:33:49
Block: 1071844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71233 RingCT/type: yes/0
Extra: 0162e7645491f4a42aa4bc2e19b749a5c79456d2400d2a1d94559c0eeaeb861bb4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf86fd13d1db8a51fc842852f7a9a957d63fcefcedbbcd3c2aa49f1739de373 0.600000000000 1544229 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": 1071854, "vin": [ { "gen": { "height": 1071844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf86fd13d1db8a51fc842852f7a9a957d63fcefcedbbcd3c2aa49f1739de373" } } ], "extra": [ 1, 98, 231, 100, 84, 145, 244, 164, 42, 164, 188, 46, 25, 183, 73, 165, 199, 148, 86, 210, 64, 13, 42, 29, 148, 85, 156, 14, 234, 235, 134, 27, 180, 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