Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238155785c0a8783e1c9424231f9090b36a855cb5c255e625a0882a9fd835799

Tx prefix hash: 4ae7f3fe4bb5c5a43dec5f45afc9630cee3831ecbd993fcef16032e9d3e3ecbb
Tx public key: 73f06772aa40f0771170001c286e1eb632d8d5100f4181c6f5ecafad0c4ed738
Timestamp: 1580895869 Timestamp [UCT]: 2020-02-05 09:44:29 Age [y:d:h:m:s]: 05:064:10:26:24
Block: 59211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197995 RingCT/type: yes/0
Extra: 0173f06772aa40f0771170001c286e1eb632d8d5100f4181c6f5ecafad0c4ed73802110000000d2264afe6000000000000000000

1 output(s) for total of 390.670120810000 dcy

stealth address amount amount idx
00: 960460d1ffc26750eb5c71d840ceae2f642e1f671139f51310bf74fc6aac4e9a 390.670120810000 109301 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": 59221, "vin": [ { "gen": { "height": 59211 } } ], "vout": [ { "amount": 390670120810, "target": { "key": "960460d1ffc26750eb5c71d840ceae2f642e1f671139f51310bf74fc6aac4e9a" } } ], "extra": [ 1, 115, 240, 103, 114, 170, 64, 240, 119, 17, 112, 0, 28, 40, 110, 30, 182, 50, 216, 213, 16, 15, 65, 129, 198, 245, 236, 175, 173, 12, 78, 215, 56, 2, 17, 0, 0, 0, 13, 34, 100, 175, 230, 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