Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee09b325c46f155c5a3eb515d5e1bd932c110bb984db3f5339b95486a06f2635

Tx prefix hash: 562817fc60754b28c37548b208b017d4f6a1045bbec4e0d13bcd5ccd444a1f30
Tx public key: bf5a625fc8f50849aeb253e2b651b438f7d3283472a0d57590cbc58bf9dd1843
Timestamp: 1722625908 Timestamp [UCT]: 2024-08-02 19:11:48 Age [y:d:h:m:s]: 00:114:06:25:09
Block: 1079329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81744 RingCT/type: yes/0
Extra: 01bf5a625fc8f50849aeb253e2b651b438f7d3283472a0d57590cbc58bf9dd184302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c345797667ce4f9805bee5fb1b2fc3a52713aa5412c7e0a28473f176a490e612 0.600000000000 1552238 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": 1079339, "vin": [ { "gen": { "height": 1079329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c345797667ce4f9805bee5fb1b2fc3a52713aa5412c7e0a28473f176a490e612" } } ], "extra": [ 1, 191, 90, 98, 95, 200, 245, 8, 73, 174, 178, 83, 226, 182, 81, 180, 56, 247, 211, 40, 52, 114, 160, 213, 117, 144, 203, 197, 139, 249, 221, 24, 67, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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