Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22db124147b8efdd9f142ba97b2cc2d6d95e4ccb6dd7b48b14a3defb35d09fe4

Tx prefix hash: 7c623887090c35552258dd203936f48974be1ca20228adb4ee4040a5089d3926
Tx public key: 2d64daf776f21a186bb17581e8f8b79ce1a8b2946cd6abed264e9d901f8127ee
Timestamp: 1726388069 Timestamp [UCT]: 2024-09-15 08:14:29 Age [y:d:h:m:s]: 00:059:02:20:40
Block: 1110521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42236 RingCT/type: yes/0
Extra: 012d64daf776f21a186bb17581e8f8b79ce1a8b2946cd6abed264e9d901f8127ee021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a15d1a2515165d41e8ae024e5ce761885f6989c407a0a069b3ba71bc0e9b379 0.600000000000 1589156 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": 1110531, "vin": [ { "gen": { "height": 1110521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a15d1a2515165d41e8ae024e5ce761885f6989c407a0a069b3ba71bc0e9b379" } } ], "extra": [ 1, 45, 100, 218, 247, 118, 242, 26, 24, 107, 177, 117, 129, 232, 248, 183, 156, 225, 168, 178, 148, 108, 214, 171, 237, 38, 78, 157, 144, 31, 129, 39, 238, 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