Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5663085aa5caad81261ae0867a3d610e6ac60226906875188fb50563d480c02

Tx prefix hash: e0c0c5a036729d08f6b56e2f86929a8c47ce1d3813cfbc7d7085592a4fee8677
Tx public key: 9a90453c57c642ca4d75e8608a76c0909eae3a669877b512d1fda635d166a3e9
Timestamp: 1731910397 Timestamp [UCT]: 2024-11-18 06:13:17 Age [y:d:h:m:s]: 00:005:22:34:58
Block: 1156202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4254 RingCT/type: yes/0
Extra: 019a90453c57c642ca4d75e8608a76c0909eae3a669877b512d1fda635d166a3e9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8634ee3f612f0bcf9f8a00e89e88a11400e140b58a5cc3354c00f147a7dd69f1 0.600000000000 1641825 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": 1156212, "vin": [ { "gen": { "height": 1156202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8634ee3f612f0bcf9f8a00e89e88a11400e140b58a5cc3354c00f147a7dd69f1" } } ], "extra": [ 1, 154, 144, 69, 60, 87, 198, 66, 202, 77, 117, 232, 96, 138, 118, 192, 144, 158, 174, 58, 102, 152, 119, 181, 18, 209, 253, 166, 53, 209, 102, 163, 233, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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