Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52fc05bbb3537ad47d5e772acb59c714d6f30c5025e951fb7b0957f9c369bdc6

Tx prefix hash: 279d7b291fc1609e42312a5459332586daa2478e8bfc423a52c05fa883ba053d
Tx public key: 4773eedf1e896e06442c2b7d51187945d84a06eefa724917ddb539f04a76f2e0
Timestamp: 1694714313 Timestamp [UCT]: 2023-09-14 17:58:33 Age [y:d:h:m:s]: 01:215:11:33:08
Block: 848107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415099 RingCT/type: yes/0
Extra: 014773eedf1e896e06442c2b7d51187945d84a06eefa724917ddb539f04a76f2e002110000000133af99f4000000000000000000

1 output(s) for total of 0.950319197000 dcy

stealth address amount amount idx
00: cc83a6ae284a0ca34ed6f049c90a79d2a48400867a75b43958b91d68abbb6bb1 0.950319197000 1301691 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": 848117, "vin": [ { "gen": { "height": 848107 } } ], "vout": [ { "amount": 950319197, "target": { "key": "cc83a6ae284a0ca34ed6f049c90a79d2a48400867a75b43958b91d68abbb6bb1" } } ], "extra": [ 1, 71, 115, 238, 223, 30, 137, 110, 6, 68, 44, 43, 125, 81, 24, 121, 69, 216, 74, 6, 238, 250, 114, 73, 23, 221, 181, 57, 240, 74, 118, 242, 224, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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