Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23fe0edcada5aa3334263cc5519e8a77379c0a82d4f031b5351c5ad6eab257e9

Tx prefix hash: 544d7a5a6c229056b33c9ea1b61a0492863f7dede409d0ab92efadac77cecfc6
Tx public key: f94f02cd28f054400434052e39d04534ace0a5f3696b4e414b6506adf7bcc727
Timestamp: 1681504704 Timestamp [UCT]: 2023-04-14 20:38:24 Age [y:d:h:m:s]: 02:017:08:53:03
Block: 738648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534568 RingCT/type: yes/0
Extra: 01f94f02cd28f054400434052e39d04534ace0a5f3696b4e414b6506adf7bcc7270211000000045029cbac000000000000000000

1 output(s) for total of 2.190547972000 dcy

stealth address amount amount idx
00: f76e427cc7ed1dd33ab4585e098d30281cbf1f8a60c13f36a4ecb1ceaddcca81 2.190547972000 1185377 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": 738658, "vin": [ { "gen": { "height": 738648 } } ], "vout": [ { "amount": 2190547972, "target": { "key": "f76e427cc7ed1dd33ab4585e098d30281cbf1f8a60c13f36a4ecb1ceaddcca81" } } ], "extra": [ 1, 249, 79, 2, 205, 40, 240, 84, 64, 4, 52, 5, 46, 57, 208, 69, 52, 172, 224, 165, 243, 105, 107, 78, 65, 75, 101, 6, 173, 247, 188, 199, 39, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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