Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db21f29d5c879c6bbbf3af894473b93599ec25f557f10bf4897b4c545e06c5b

Tx prefix hash: 53769af93232c4d7eabeafb02d00909f0a9460f0bad9a7fbf2f0bc9def788305
Tx public key: e0351a5edec51ddc4408040074af5ac118700467a4d804f90a509e0c99c5b884
Timestamp: 1722315311 Timestamp [UCT]: 2024-07-30 04:55:11 Age [y:d:h:m:s]: 00:299:14:04:23
Block: 1076749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214059 RingCT/type: yes/0
Extra: 01e0351a5edec51ddc4408040074af5ac118700467a4d804f90a509e0c99c5b884021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2f128f3b58966c263780bb4f845df0e4ab5daac3d52a8cf5c2084d505f0c595 0.600000000000 1549290 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": 1076759, "vin": [ { "gen": { "height": 1076749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2f128f3b58966c263780bb4f845df0e4ab5daac3d52a8cf5c2084d505f0c595" } } ], "extra": [ 1, 224, 53, 26, 94, 222, 197, 29, 220, 68, 8, 4, 0, 116, 175, 90, 193, 24, 112, 4, 103, 164, 216, 4, 249, 10, 80, 158, 12, 153, 197, 184, 132, 2, 17, 0, 0, 0, 9, 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