Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eedf68fcb8bff7d3ef1d023a7ff6a50c1f446b6ad8385971ff89fd25ca403050

Tx prefix hash: f1b6dbd219901f61a03f2d34890acda99af71729819c6b47a17f066c02dfc2ba
Tx public key: 83c75c97f77e17bb38ea9a0a7d1c86b1793b7476ad2cafae0b97da3819e14d75
Timestamp: 1581182259 Timestamp [UCT]: 2020-02-08 17:17:39 Age [y:d:h:m:s]: 05:001:23:51:25
Block: 60889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154042 RingCT/type: yes/0
Extra: 0183c75c97f77e17bb38ea9a0a7d1c86b1793b7476ad2cafae0b97da3819e14d750211000000254ac5aa02000000000000000000

1 output(s) for total of 385.700572773000 dcy

stealth address amount amount idx
00: c4e5f3a5c816f5a8b307b59a83babbdd3060b1553832311af1e4bda931e2de0a 385.700572773000 112216 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": 60899, "vin": [ { "gen": { "height": 60889 } } ], "vout": [ { "amount": 385700572773, "target": { "key": "c4e5f3a5c816f5a8b307b59a83babbdd3060b1553832311af1e4bda931e2de0a" } } ], "extra": [ 1, 131, 199, 92, 151, 247, 126, 23, 187, 56, 234, 154, 10, 125, 28, 134, 177, 121, 59, 116, 118, 173, 44, 175, 174, 11, 151, 218, 56, 25, 225, 77, 117, 2, 17, 0, 0, 0, 37, 74, 197, 170, 2, 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