Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dba3560c93c19ee5a2d35e5f12d3b5e13d115989dd09e1db766271286b5046a9

Tx prefix hash: 26da06951353e0bc114a727847c44a26ed4c2663738e131e9d49f4097915591b
Tx public key: 4289752de53b68aa6b0ce08531c49c8a0ee6bb5adaa5f111688aaef9eba71ef8
Timestamp: 1704469228 Timestamp [UCT]: 2024-01-05 15:40:28 Age [y:d:h:m:s]: 01:098:13:37:31
Block: 928779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331569 RingCT/type: yes/0
Extra: 014289752de53b68aa6b0ce08531c49c8a0ee6bb5adaa5f111688aaef9eba71ef802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e886dc98f7fa356c5f5812fdbe9ad6e3b2c4bb0a0df9067eec5e6391fb1b6f55 0.600000000000 1386641 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": 928789, "vin": [ { "gen": { "height": 928779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e886dc98f7fa356c5f5812fdbe9ad6e3b2c4bb0a0df9067eec5e6391fb1b6f55" } } ], "extra": [ 1, 66, 137, 117, 45, 229, 59, 104, 170, 107, 12, 224, 133, 49, 196, 156, 138, 14, 230, 187, 90, 218, 165, 241, 17, 104, 138, 174, 249, 235, 167, 30, 248, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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