Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e588e6620ba71d39de885b8706c5fa906c527e87ed6e24f6b4a3d53c47165083

Tx prefix hash: 4525c33e216a335a1735e9ed8cf548254719a782c9e56e74e47ca8bf7b628136
Tx public key: d2a6029272261200061a54f8494c213945097fa4f9e9f4d456f530a33c0b6434
Timestamp: 1727521838 Timestamp [UCT]: 2024-09-28 11:10:38 Age [y:d:h:m:s]: 00:057:07:23:28
Block: 1119919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40947 RingCT/type: yes/0
Extra: 01d2a6029272261200061a54f8494c213945097fa4f9e9f4d456f530a33c0b6434021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa482fbacd6d79ea20f618df214a4fabd1d5794936f072fd9bd30395b6e16a1 0.600000000000 1601650 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": 1119929, "vin": [ { "gen": { "height": 1119919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa482fbacd6d79ea20f618df214a4fabd1d5794936f072fd9bd30395b6e16a1" } } ], "extra": [ 1, 210, 166, 2, 146, 114, 38, 18, 0, 6, 26, 84, 248, 73, 76, 33, 57, 69, 9, 127, 164, 249, 233, 244, 212, 86, 245, 48, 163, 60, 11, 100, 52, 2, 17, 0, 0, 0, 6, 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