Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516ac57fefb2edc2d97024d86a2a0b114190973aff02a34d90f03cf72e89559a

Tx prefix hash: a8add95361f4b9e1ce43cb2647de549f4347a45ce55f1e2af4695f91a9eaa706
Tx public key: 38800fd3440e0d86f1e85a2fae86c720809e8246b1765e4ff437e7d7086ceee2
Timestamp: 1696836009 Timestamp [UCT]: 2023-10-09 07:20:09 Age [y:d:h:m:s]: 01:142:01:48:36
Block: 865722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362545 RingCT/type: yes/0
Extra: 0138800fd3440e0d86f1e85a2fae86c720809e8246b1765e4ff437e7d7086ceee20211000000024b8f5122000000000000000000

1 output(s) for total of 0.830813738000 dcy

stealth address amount amount idx
00: 7a40dd74e40f04a9cef1eb179bdac090f31d20812edd73f30502ed53a9bd3265 0.830813738000 1320264 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": 865732, "vin": [ { "gen": { "height": 865722 } } ], "vout": [ { "amount": 830813738, "target": { "key": "7a40dd74e40f04a9cef1eb179bdac090f31d20812edd73f30502ed53a9bd3265" } } ], "extra": [ 1, 56, 128, 15, 211, 68, 14, 13, 134, 241, 232, 90, 47, 174, 134, 199, 32, 128, 158, 130, 70, 177, 118, 94, 79, 244, 55, 231, 215, 8, 108, 238, 226, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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