Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4776c0b43d9e95527ee4c1653b95e55855d4adf889b47774ebee29f473081d2

Tx prefix hash: a8625781eeebe66f7b5cdcde2a2f65f3bb1760ae8ded769fd43b265e819fde4d
Tx public key: 0784c6e39952e9caa922c29b37a10f09872661b0ab0d23035f7db6717bf72e57
Timestamp: 1722084153 Timestamp [UCT]: 2024-07-27 12:42:33 Age [y:d:h:m:s]: 00:260:19:07:44
Block: 1074836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186321 RingCT/type: yes/0
Extra: 010784c6e39952e9caa922c29b37a10f09872661b0ab0d23035f7db6717bf72e57021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ac848abd24c2d90f088c721401ee797ec04e89c803d2a628c9bf92f3da11a62 0.600000000000 1547355 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": 1074846, "vin": [ { "gen": { "height": 1074836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ac848abd24c2d90f088c721401ee797ec04e89c803d2a628c9bf92f3da11a62" } } ], "extra": [ 1, 7, 132, 198, 227, 153, 82, 233, 202, 169, 34, 194, 155, 55, 161, 15, 9, 135, 38, 97, 176, 171, 13, 35, 3, 95, 125, 182, 113, 123, 247, 46, 87, 2, 17, 0, 0, 0, 7, 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