Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c7d1049d745000ec08f08f2dcb0d4d83854beb77e57f950293ec3516354e5a

Tx prefix hash: 6479aa8bd6489e8615d25691158f81b0cc09a9afae28b3a58018c2154473c397
Tx public key: c92ee9816e3622779b3cae71aea10e0c76689135ae42013ee2b67c5fd262f21a
Timestamp: 1699841440 Timestamp [UCT]: 2023-11-13 02:10:40 Age [y:d:h:m:s]: 01:071:13:49:00
Block: 890445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312506 RingCT/type: yes/0
Extra: 01c92ee9816e3622779b3cae71aea10e0c76689135ae42013ee2b67c5fd262f21a02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.687996250000 dcy

stealth address amount amount idx
00: 770f71a361db79c724841b1d36bed63f7f70ce48be8454734af54cb20766f6e0 0.687996250000 1346468 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": 890455, "vin": [ { "gen": { "height": 890445 } } ], "vout": [ { "amount": 687996250, "target": { "key": "770f71a361db79c724841b1d36bed63f7f70ce48be8454734af54cb20766f6e0" } } ], "extra": [ 1, 201, 46, 233, 129, 110, 54, 34, 119, 155, 60, 174, 113, 174, 161, 14, 12, 118, 104, 145, 53, 174, 66, 1, 62, 226, 182, 124, 95, 210, 98, 242, 26, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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