Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ee1133cde09b39f2bae3b510c6adf746ab1055f884e648909832d955d1f661

Tx prefix hash: 5f7f0c31adfd08071f0963f785cd35058c305dc71e1310f70d4ae855ab62b982
Tx public key: 460205c2a608a4a7b9ba6345b86960c809fd10616c7282160b8aaef31b69d2f4
Timestamp: 1743275675 Timestamp [UCT]: 2025-03-29 19:14:35 Age [y:d:h:m:s]: 00:233:14:06:19
Block: 1250029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164685 RingCT/type: yes/0
Extra: 01460205c2a608a4a7b9ba6345b86960c809fd10616c7282160b8aaef31b69d2f40211000000061a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2a6d19e937b718f13e137df0dd20bad8853a6c2bb0aa5ca8caecec1dee53f8d 0.600000000000 1737076 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": 1250039, "vin": [ { "gen": { "height": 1250029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2a6d19e937b718f13e137df0dd20bad8853a6c2bb0aa5ca8caecec1dee53f8d" } } ], "extra": [ 1, 70, 2, 5, 194, 166, 8, 164, 167, 185, 186, 99, 69, 184, 105, 96, 200, 9, 253, 16, 97, 108, 114, 130, 22, 11, 138, 174, 243, 27, 105, 210, 244, 2, 17, 0, 0, 0, 6, 26, 151, 4, 3, 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