Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d6afded11c4ed0dc1f1211978c74d5331dedff05328cd24ee758a0f7862f6e

Tx prefix hash: 04362036962a893b9960ee05c9687bdca35b2077c437392b33e5a6cf3da5bcb8
Tx public key: 1b936106894179860ea71d39d576f2aa1843db7b547844bcd50ade33dc00e315
Timestamp: 1581509330 Timestamp [UCT]: 2020-02-12 12:08:50 Age [y:d:h:m:s]: 04:288:14:10:11
Block: 63369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098450 RingCT/type: yes/0
Extra: 011b936106894179860ea71d39d576f2aa1843db7b547844bcd50ade33dc00e315021100000002d81c26c0000000000000000000

1 output(s) for total of 378.471351186000 dcy

stealth address amount amount idx
00: f65878cf116b5e922c2cd8414c0cda0f33c29739e5b9e6fcc0fbbe980caf3c35 378.471351186000 116871 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": 63379, "vin": [ { "gen": { "height": 63369 } } ], "vout": [ { "amount": 378471351186, "target": { "key": "f65878cf116b5e922c2cd8414c0cda0f33c29739e5b9e6fcc0fbbe980caf3c35" } } ], "extra": [ 1, 27, 147, 97, 6, 137, 65, 121, 134, 14, 167, 29, 57, 213, 118, 242, 170, 24, 67, 219, 123, 84, 120, 68, 188, 213, 10, 222, 51, 220, 0, 227, 21, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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