Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f07dde30b81464524e4102aaddb55cb0bb6866172272d1893e4e411a10e0dc

Tx prefix hash: 80abb7327c39c780c2421b3afd63d51ed04e27fe2b2204cfa2c9159664a0c48c
Tx public key: 53407749a5f8bc138cd491e52bbfcc0c05f600f37cde9d0c072450cb006a3a52
Timestamp: 1577893936 Timestamp [UCT]: 2020-01-01 15:52:16 Age [y:d:h:m:s]: 05:136:01:13:50
Block: 36411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247177 RingCT/type: yes/0
Extra: 0153407749a5f8bc138cd491e52bbfcc0c05f600f37cde9d0c072450cb006a3a520211000000084943cd9f000000000000000000

1 output(s) for total of 464.896305585000 dcy

stealth address amount amount idx
00: 3366108616cd91e89f1762f5b7e86faeccd8ff6302bfd8a35a029ae4760d158f 464.896305585000 61690 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": 36421, "vin": [ { "gen": { "height": 36411 } } ], "vout": [ { "amount": 464896305585, "target": { "key": "3366108616cd91e89f1762f5b7e86faeccd8ff6302bfd8a35a029ae4760d158f" } } ], "extra": [ 1, 83, 64, 119, 73, 165, 248, 188, 19, 140, 212, 145, 229, 43, 191, 204, 12, 5, 246, 0, 243, 124, 222, 157, 12, 7, 36, 80, 203, 0, 106, 58, 82, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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