Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 808a78277288f49d0fecbd263d322513d80528bf8d1ca59176acbda248c86874

Tx prefix hash: bf43f393d89e8e23b52082b5c6adaab3c182cb349b5a3fed872ccae8bdd5f56e
Tx public key: 52be2be9c810899e5f0f9f5d8aeda09fa94a47f4d7f4eaa5bd455843d3ffa84f
Timestamp: 1718758459 Timestamp [UCT]: 2024-06-19 00:54:19 Age [y:d:h:m:s]: 01:142:21:24:55
Block: 1047269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360676 RingCT/type: yes/0
Extra: 0152be2be9c810899e5f0f9f5d8aeda09fa94a47f4d7f4eaa5bd455843d3ffa84f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14c2524fe294a3d7e60c80d24aeec728afc4ad7f0f2728f307d2f41ce4a3acb5 0.600000000000 1517088 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": 1047279, "vin": [ { "gen": { "height": 1047269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14c2524fe294a3d7e60c80d24aeec728afc4ad7f0f2728f307d2f41ce4a3acb5" } } ], "extra": [ 1, 82, 190, 43, 233, 200, 16, 137, 158, 95, 15, 159, 93, 138, 237, 160, 159, 169, 74, 71, 244, 215, 244, 234, 165, 189, 69, 88, 67, 211, 255, 168, 79, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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