Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ebb6bb49233e99a5bf89fb9f3f8a2e6d33851d2b7702dd26465cea67af78224

Tx prefix hash: 4da7d5a2dae7b1b6846ddaa991765fd480da1c1e8af9c269426c5d073057d383
Tx public key: 144dd79da643f83322edbdd776fce7ff5415a8d015db4b8976735c78af8d7cb9
Timestamp: 1580007641 Timestamp [UCT]: 2020-01-26 03:00:41 Age [y:d:h:m:s]: 04:336:19:38:32
Block: 52864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131017 RingCT/type: yes/0
Extra: 01144dd79da643f83322edbdd776fce7ff5415a8d015db4b8976735c78af8d7cb9021100000001dcee4b4d000000000000000000

1 output(s) for total of 410.053432717000 dcy

stealth address amount amount idx
00: bdfa91e0f7be56e1a2ca1f6a6c077c908a0c2a439322aa2e38a292d9890e2c4e 410.053432717000 98092 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": 52874, "vin": [ { "gen": { "height": 52864 } } ], "vout": [ { "amount": 410053432717, "target": { "key": "bdfa91e0f7be56e1a2ca1f6a6c077c908a0c2a439322aa2e38a292d9890e2c4e" } } ], "extra": [ 1, 20, 77, 215, 157, 166, 67, 248, 51, 34, 237, 189, 215, 118, 252, 231, 255, 84, 21, 168, 208, 21, 219, 75, 137, 118, 115, 92, 120, 175, 141, 124, 185, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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