Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e77717d059d69de3703348e7fb4a6e735a65f3bd7c62cdaff287bd33a34ac3e5

Tx prefix hash: c91ba0383346901862590f281b8aa4bc8fc8e88dd21784d0beed4eb1a7070488
Tx public key: e2815395e952914386d90acf8320da37b7c0477915e7a2cb4df3a7d01963b7b0
Timestamp: 1702330972 Timestamp [UCT]: 2023-12-11 21:42:52 Age [y:d:h:m:s]: 01:332:17:27:26
Block: 911079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496649 RingCT/type: yes/0
Extra: 01e2815395e952914386d90acf8320da37b7c0477915e7a2cb4df3a7d01963b7b002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ee3e4ff93b478ec0f0d46711c308693e2aaff050a8eb34709d2206249a3681 0.600000000000 1368254 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": 911089, "vin": [ { "gen": { "height": 911079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ee3e4ff93b478ec0f0d46711c308693e2aaff050a8eb34709d2206249a3681" } } ], "extra": [ 1, 226, 129, 83, 149, 233, 82, 145, 67, 134, 217, 10, 207, 131, 32, 218, 55, 183, 192, 71, 121, 21, 231, 162, 203, 77, 243, 167, 208, 25, 99, 183, 176, 2, 17, 0, 0, 0, 4, 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