Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fc6f64f51f88409d5bafb6add3af1f3b3ebe3268745a1f00f9d356f4ad6b041

Tx prefix hash: a86c3ffe835c17fcfa78b981af901eb7785439b2961ee70f9ec60663cd8c63f3
Tx public key: 5a0be4d7259f3ef9ec4d158eb12e2c52dfa672363380d78337f813b293a9b54e
Timestamp: 1626679288 Timestamp [UCT]: 2021-07-19 07:21:28 Age [y:d:h:m:s]: 03:134:09:08:34
Block: 296777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 867615 RingCT/type: yes/0
Extra: 015a0be4d7259f3ef9ec4d158eb12e2c52dfa672363380d78337f813b293a9b54e02110000000a9cd60737000000000000000000

1 output(s) for total of 63.775679751000 dcy

stealth address amount amount idx
00: 0ffb72eba8ac44c544fc047b3746a351a6d1a156e4e6547dcfe314162e757c83 63.775679751000 621237 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": 296787, "vin": [ { "gen": { "height": 296777 } } ], "vout": [ { "amount": 63775679751, "target": { "key": "0ffb72eba8ac44c544fc047b3746a351a6d1a156e4e6547dcfe314162e757c83" } } ], "extra": [ 1, 90, 11, 228, 215, 37, 159, 62, 249, 236, 77, 21, 142, 177, 46, 44, 82, 223, 166, 114, 54, 51, 128, 215, 131, 55, 248, 19, 178, 147, 169, 181, 78, 2, 17, 0, 0, 0, 10, 156, 214, 7, 55, 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