Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234fc39b7abcf07c2c20f8a261f8cda4ef2d16cd6db77b902d58000c4213027e

Tx prefix hash: 5bd0a7f43239045335d79fa259cfc8a4e22772759925c82151824aec6fd74fcd
Tx public key: e1d3821897f4edff802a1da6ba3f7dd81662db79e1a10179efd5dc6023d5f4be
Timestamp: 1723376956 Timestamp [UCT]: 2024-08-11 11:49:16 Age [y:d:h:m:s]: 01:087:11:39:55
Block: 1085554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320979 RingCT/type: yes/0
Extra: 01e1d3821897f4edff802a1da6ba3f7dd81662db79e1a10179efd5dc6023d5f4be021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 221c0fb59172262ca43c70222ecbe38eb20181250e162c4fcc6558b3001c51e5 0.600000000000 1560141 of 15

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": 1085564, "vin": [ { "gen": { "height": 1085554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "221c0fb59172262ca43c70222ecbe38eb20181250e162c4fcc6558b3001c51e5" } } ], "extra": [ 1, 225, 211, 130, 24, 151, 244, 237, 255, 128, 42, 29, 166, 186, 63, 125, 216, 22, 98, 219, 121, 225, 161, 1, 121, 239, 213, 220, 96, 35, 213, 244, 190, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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