Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662f8f381310fe0e8068c01d484ca1a7841f0e25e2b369ce16d1a0f2303cab71

Tx prefix hash: 768dac6778fafb552763eb32abcb443af6e6d7811a81a2dbb90f14ab72e85936
Tx public key: 9902abed9e4529ab92e2cc8ba7c4f4fded1d031f53f5b1861914823b71bd77f3
Timestamp: 1583639936 Timestamp [UCT]: 2020-03-08 03:58:56 Age [y:d:h:m:s]: 04:254:12:03:53
Block: 78544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076509 RingCT/type: yes/0
Extra: 019902abed9e4529ab92e2cc8ba7c4f4fded1d031f53f5b1861914823b71bd77f30211000000178e602c4c000000000000000000

1 output(s) for total of 337.094692682000 dcy

stealth address amount amount idx
00: fc5cc2cd7e1d3f12ee9dc94f322d2f34dfc0b0d12b55cc25e783bb5fbcb2fdd7 337.094692682000 144006 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": 78554, "vin": [ { "gen": { "height": 78544 } } ], "vout": [ { "amount": 337094692682, "target": { "key": "fc5cc2cd7e1d3f12ee9dc94f322d2f34dfc0b0d12b55cc25e783bb5fbcb2fdd7" } } ], "extra": [ 1, 153, 2, 171, 237, 158, 69, 41, 171, 146, 226, 204, 139, 167, 196, 244, 253, 237, 29, 3, 31, 83, 245, 177, 134, 25, 20, 130, 59, 113, 189, 119, 243, 2, 17, 0, 0, 0, 23, 142, 96, 44, 76, 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